DOC: added answers to questions
Browse files- BuildingAChainlitApp.md +8 -0
BuildingAChainlitApp.md
CHANGED
|
@@ -186,6 +186,14 @@ Now, we'll save that into our user session!
|
|
| 186 |
|
| 187 |
Why are we using User Session here? What about Python makes us need to use this? Why not just store everything in a global variable?
|
| 188 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 189 |
## On Message
|
| 190 |
|
| 191 |
First, we load our chain from the user session:
|
|
|
|
| 186 |
|
| 187 |
Why are we using User Session here? What about Python makes us need to use this? Why not just store everything in a global variable?
|
| 188 |
|
| 189 |
+
The application hopefully will be run by many people, at the same time. If the data was stored in a global variable
|
| 190 |
+
this would be accessed by everyone using the application. So everytime someone started a new session, the information
|
| 191 |
+
would be overwritten, meaning everyone would basically get the same results. Unless only one person used the system
|
| 192 |
+
at a time.
|
| 193 |
+
|
| 194 |
+
So the goal is to keep each users session information separate from all the other users. The ChainLit User session
|
| 195 |
+
provides the capability of storing each users data separately.
|
| 196 |
+
|
| 197 |
## On Message
|
| 198 |
|
| 199 |
First, we load our chain from the user session:
|