I'd like connection local storage that lasts the lifetime of a client
connection to the server, i.e. as long as the socket is open.
AOLserver terminology is whacked -- it defines a connection as an HTTP
request, and a request as the actual 'GET / HTTP/1.0' line. So I guess
what I'd like is 'socke
On Thursday 10 June 2004 22:03, you wrote:
> This sounds like Connection Local Storage type of need. There is a set
> of api's available in aolserver 4.0 which implement this, which you
> might find interesting:
>
> http://www.aolserver.com/40drafts/capi/api/newindex.htm
>
> Specifically, for exam
On 2004.06.10, Mike Schilli <[EMAIL PROTECTED]> wrote:
> to manage a global data structure over the course of a single request,
> we were thinking about having a global hash table, indexed by the
> address returned by Ns_GetConn().
>
> This way, every function could access the request-specific data
This sounds like Connection Local Storage type of need. There is a set
of api's available in aolserver 4.0 which implement this, which you
might find interesting:
http://www.aolserver.com/40drafts/capi/api/newindex.htm
Specifically, for example,
http://www.aolserver.com/40drafts/capi/api/c40-02
On Thursday 10 June 2004 21:47, you wrote:
> Hi all,
>
> to manage a global data structure over the course of a single request,
> we were thinking about having a global hash table, indexed by the
> address returned by Ns_GetConn().
>
> This way, every function could access the request-specific data
Hi all,
to manage a global data structure over the course of a single request,
we were thinking about having a global hash table, indexed by the
address returned by Ns_GetConn().
This way, every function could access the request-specific data by
calling Ns_GetConn(), obtaining a unique "request-i
