At 09:47 AM 5/21/99 -0700, Johnston, Brendan wrote:
. . .

>
>From an implementation point of view there is no need to involve the session
>engine.  These values will now be hanging around in the persistence engine
>for not particular purpose till the session ends.  These values could just
>as easily go in a query parameters object which could be a page instance
>variable or even better just an argument to a new load function in the
>target page.   
>Here is place a web hit object which lasts for this web event could be
>useful.  I know that people love the session stuff because it is simple, but
>I just hate global variables.

-- Strongly agree.  Actually, there is already a web hit object, this being
the hashtable that is loaded with existing session values from the PE at
the start of the web event, and from which the PE is reloaded at the end of
the web event.  When, in the course of a web event, you put a session
object in a button method in PageA, load PageB, and then in PageB's
onBeforeLoad event you retrieve the value, you are simply executing 'put'
and 'get' on the local hashtable.  The problem, or at least a problem, is,
as Brendan noted, is that the value will be copied to the PE at the end of
web event, and then retrieved in every subsequent web event (yes, there are
some options to control this), even if its value will be reset each time it
is used in a web event.

No doubt a robust web hit object would have more than just the hashtable,
and it would probably be desirable to be able to create local subclasses,
and all that, but ND could get us part of the way there just by providing
some method to add a value to the hashtable, or a new signature of
Put(Any)UserSessionObject, that would indicate that the value is not to be
copied to the PE at the end of the web event.

-- Curt Springer, Team ND


_________________________________________________________________________

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]

Reply via email to