No, it's all memory. But, you have to remember that session attributes stay in memory for the life of the session (which typically spans many requests and perhaps all day long), whereas request attributes stay in memory for the life of the request. In other words, requests don't really require "cleanup", but sessions might.

Lookup performance is the same; they are hash-based.

Use request scope for items that are only needed to service the current request. Use session scope for items that are needed to service a particular user during the span of multiple requests. Use application scope for items that are needed to service any user at any given time (closest scope to being truly "static").

Erik


wo_shi_ni_ba_ba wrote:

In terms of performance, does storing an attribute
into the session cost more than storing it into the
request? how significant is the overhead?



__________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to