Re: Serialized continuation size

On Mon, Apr 24, 2006 at 10:02:45AM -0700, Dan wrote:
> Thanks for your prompt response.
> > Actually, checking now, if a procedure is defined in
> > a named symbolic 
> > environment, a reference to that procedure is
> > serialized instead.  So toplevel references, 
> > including toplevel defined module exports, won't be
> > serialized in there entirety.
> 
> By "not in their entirety" you mean just the reference
> is serialized -- right?

Yes.

> 
> > > ensure this? Do I need to create new heap files?
> > 
> > What are you concerned about exactly?  
> 
> Continuation size. I intend to serialize webapp
> continuations *in the HTTP response*, as part of the
> URLs for href anchors and form action's. That is, the
> webapp HTTP response will include fragments like:
> 
> <a href="blahblahblahblah...">Continue to second
> page</a>
> 
> where blahblah... will be an encoded continuation.
> Thus, the continuations need to be as small as
> possible (obeying the URL length limit).
> 
> If this works, it will be totally awesome :)

That may be tricky.  I suspect you won't be able to get your 
continuations down to under a couple hundred bytes, which would still be 
an awefully long URL.  There are security concerns also of course, since
the client could alter the continuation and do any number of strange 
things.

> So -- if I create a new heap JAR, would I be able to
> completely avoid serialization of code?

Except for the parts of active expressions on the stack.

	Scott



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642