You should not store a large amount of data in the session. The
session is stored in a cookie, and everything you store there has to
be sent back and forth over the network. You can however store an ID
in the session and lookup data in your database.
// Magnus Holm
On Tue, Dec 3, 2013 at 12:04 P
Sure wish the W3C would devise a better state mechanism than cookies...
On Dec 6, 2013, at 12:49 PM, Magnus Holm wrote:
> You should not store a large amount of data in the session. The
> session is stored in a cookie, and everything you store there has to
> be sent back and forth over the netwo
If you fill the session cookie with 4kb of data, that means every http request
after that to that domain will require the user to upload 4kb of data, which
may not seem like much, but on a mobile phone for instance, loading a page with
50 images, that becomes 4*50 = 200kb - pretty significant co
3 matches
Mail list logo
