Don't take it badly but (bandwidth point of vue)
I believe it's not normal to send a string of 2000 char back to a server.
It means that the server also send 2000 char etc...
I suppose this big string comes from a page session object
containing too much information.
Why not creating a user session object in CSpHashTable format.
The browser then just send a reference id to find a pseudo page session object
in the CSpHashTable.
I agree it takes space on the server but it's also a work around
for another kind of problem:
-think about a list of href and each item is suppose to send a page session...
By this mean I reduced a page from 120Kb to 12Kb!
Serge.
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
>Hello,
>We're using the CSpHttpProxy service to communicate between the client and server.
>However, we're running up against a maximum URL length of 2000 characters in Internet
>Explorer 4.0x.
>The Netdynamics encoding of an object, along with all the page session, quickly
>reaches this limit.
>Has anyone come up against a similar problem and found a work around?
>
>thanks
>Steve Crossan
>Fidelity Investments
_________________________________________________________________________
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]
