Yes, I understand the difference between HTTP POST and GET requests.
The issue with ND is, what is stopping ND from treating the value
of a hidden any differently, than say a page session variable? ND
could _easily_ encode the value of the hidden into the HREF if it
wanted to. A hidden is constant, unlike say a textbox, or combobox.
I don't like the onBeforeHtmlOutputEvent() approach, because it seems
too easy for a user to change the value in the URL. Page session
variables are encoded/encrypted with the other the session values,
and therefore are much harder to mess with. And in either case the
URL will get longer, and without testing it, I cannot say which makes
a shorter URL (generally speaking).
Nice talking to you.
Take care,
Ryan
Grace Frederick wrote:
>
> > I tried to do it that way originally too. It doesn't work, because ND
> > will not let an HREF send the value of a hidden field (at least thru
> > the studio interface). But, it _can_ send the value of a page session
> > object. So, in addition to putting the value into the hidden field,
> > also put it into a page session object. Then setup the HREF to send
> > the page session object to the next page.
>
> The limitation in sending hidden form field values via HREFs isn't an ND
> issue. Form fields are sent via the CGI buffer. HREFs send values by
> attaching them to the URL. The reason why page session objects work is
> because ND adds it to the session information, serializes/encrypts the
> information, and attaches the result to the SRC URL in the HREF tag.
>
> Be careful about stuffing too much data in page session objects though.
> Very little, if any, compression is done on the session information when
> it's attached to the URL, so the more information that's saved in page
> session objects, the longer the URL.
>
> Another approach would be to use the onBeforeHtmlOutputEvent for the HREF to
> append a name-value pair to the URL. Then, use the onBeforeDisplayEvent of
> the next page to get the NVP.
>
> -- Grace
>
> PS... Don't beat me up if the page session variables aren't actually
> serialized in the Java sense. I'm not exactly sure what ND does to generate
> the session variable that's appended to the URL in an HREF. But the general
> concept is the same.
_________________________________________________________________________
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]
