Re: IceBreak as an alternative to Apache?

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Typically there's a session ID somewhere in the transaction that's used 
to retrieve all the appropriate state information.  The state 
information is persisted (the fancy name for "written to disk") on every 
request and then retrieved on the next request.  As you might guess, 
this adds significant overhead.  It's particularly painful when you need 
to re-open and reposition database cursors.

Joe

> Just as a question
>
> How do you all manage state in the HTTP stateless environment? What is
> state?
>
> Happy new year
>
> Maurice O'Prey