so, please allow me to clarify, because TCP/IP is connectionless, cookies were implemented to give the client and server a software-based connection by allowing the client to send back its state to the server and the server can read and process that state to know what to do in the next step. correct so far?
web2py automatically and always sets up a new session, or uses an existing one, if the client either does not send back a cookie containing the session id or it does, respectively. correct? so the client cookie really only needs that cookie containing only the session id because we as developers can and should store any state or cross function data in the session. correct? the session data is actually only local to the server itself, for it is storing its data on the server itself and not actually sending all of that data to and fro the client computer. correct? because, and i reiterate, the cookie which is traveling between client and server is really only storing the session id, which is opened and reimplemented everytime a new request comes in from the client. correct? just wanting to make sure that i am understanding the dynamics of web2py here. please elaborate as necessary on any of the details or gaps i may have introduced. ok? thanx in advance. lucas -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
