As I said earlier, with which Aby concurred, is that putting to and getting from a _page_ session object could be a problem in the same web event, and your chain of events is in the same web event. It's enough for me that ND says it is not supported. Whether it will or won't work in a specific instance is not worth the time to experiment. Actually, I did experiment, a lot, about 3 years ago when ND documentation was not as wonderful as it is now </sarcasm>. In your latest, you said "session". If you put/get to/from the user session, not page session, that's a different animal. If you put a session object during a web event, it is put into a local hashtable. During the web event, it will be retrieved from the local hashtable on a get. At the end of the web event, the contents of the hashtable are moved to the PE. I don't know why ND supports 'interim' putting/getting for session objects and not page session objects. I believe that page session objects are also stored in a local hash table. At 10:53 AM 3/12/99 -0800, [EMAIL PROTECTED] wrote: >Thanks Aby, Curt, > >I think using member variable is alot cleaner approach. >But is there a specific situation where using the page session >in the way I described will fail ? > >( I use the this_onBeforeDisplayEvent on the page > to session a hashtable of user specific data that I extract from cgi web variables. > These web variable is coded in an href on the previous page.) > >Suyoto > >Curt Springer <[EMAIL PROTECTED]> wrote: >>At 01:01 PM 3/12/99 -0500, Mathew, Aby wrote:>>Suyoto, >>> >>>You can think of member variables as your own throught the course of a Web >>>event. The only limitation is, another web event later on should not expect >>>to find what was left in the previous web event. >>> >>>However, I won't be surprised if you have some problems with what you are >>>doing. PUTTING a pageSessionObject and later GETTING it within a web event >>>doesn't make sense and is not guaranteed to work from what I know. The >>>purpose of a pageSessionObject is to attach something to a page (somewhere >>>hidden in the SPIDERSESSION value) so that you can get it back later when >>>the page is submitteed >>^^^^^^^^^^^^^ >>Quite right. I recall a specific warning _not_ to do this, basically >>saying that if you 'put' a page session value, you will not 'get' that >>value until the _next_ web event. Plus which, there is the issue of huge >>encrypted page session strings blowing up browsers, one more reason not to >>cram stuff in there that you don't need. >> >>Anybody who says the solution to 'session-bleeding' in ND is _never_ to use >>member variables is wrong and maybe even dangerous!! >>(Brendan, hold your tongue about people who make categorical statements >>about data objects ;-) ). >> >>-- Curt, =E9quipe ND, une petite division minuscule de Sun >> >> >> >>> >>>Hope this helps. >>> >>>Aby Mathew >>> >>>> -----Original Message----- >>>> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] >>>> Sent: Friday, March 12, 1999 12:39 PM >>>> To: [EMAIL PROTECTED] >>>> Subject: [ND] Member variable value along a chain of event >>>>=20 >>>> I have a pagesession object that was set in the this_onbeforedisplay= >> event >>>> of the page. >>>> If I assigned this pagesession object to a member variable, can I be >>>> assured that >>>> the value will be not be changed by other session along this chain of >>>> event: >>>>=20 >>>> this_onBeforeDisplayEvent() =3D> variable set=20 >>>> stDisplayField_onBeforeDisplayEvent() =3D> stDisplayField is located on >>>> the same page >>>> stDisplayField_onBeforeHtmlOutputEvent()=20 >>>>=20 >>>> I saw a few postings about this subject but could not determine whether >>>> the postings meant within a single event method or along a chain of event >>>> methods that >>>> were triggered by a user action. >>>>=20 >>>> Any help is really appreciated. This will save a lot of function calls in >>>> my page. >>>>=20 >>>> Suyoto Tandio ([EMAIL PROTECTED]) >>>>=20 >>>> _________________________________________________________________________ >>>>=20 >>>> For help in using, subscribing, and unsubscribing to the discussion >>>> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html >>>>=20 >>>> 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] >>> >> > >_________________________________________________________________________ > >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]
