If you are talking about related items of information that are stored and
retrieved together, I would certainly prefer putting it in a (CSp)Hashtable
and creating one UserSessionObject. It simply looks a cleaner way of doing
it.
It could be marginally or substantially (can somebody make it more precise?)
more efficient since there will be only a single request from CP to PE when
you store/retrieve the object.
Aby
TeamND
> -----Original Message-----
> From: Lundgren, Rusty [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 12, 1999 8:24 AM
> To: '[EMAIL PROTECTED]'
> Subject: [ND] Session Objects
>
>
> Hi,
>
> I was wondering if someone can help me with this.
>
> What are the performance differences ( or any differences )
> between using
> say 25 different CSpUserSessionObjects, as opposed to using 1
> Hash Table in
> a CSpUserSessionObject that contains all my 25 variables?
>
> Thanks,
>
> Rusty
> ______________________________________________________________
> ___________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to:
> http://www.netdynamics.com/support/visitdevfor.> html
>
> For dire
> need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
