Hi Ian,
Good to hear someone is using it!
I guess I didn't document it very well. You need to pass it a valid
HTTP time string. The easy way to get it to never expire is to pass
the value of:
[ns_httptime 2000000000]
That tells it to expire "Wed, 18 May 2033 03:33:20 GMT", which ought
to be long enough in the future! :)
Cheers,
Bas.
On 20 Jun 2007, at 05:04, Ian Harding wrote:
Hello,
I am trying to use ns_cookie for the first time and am not having any
luck getting a persistent cookie set. Session cookies seem to get set
regardless of the value I send for expires. Am I doing something
wrong?
ns_session is working great, this is the first time I tried to use the
ns_cookie commands.
Thanks,
Ian
On 2/24/06, Bas Scheffers <[EMAIL PROTECTED]> wrote:
Jeremy Collins wrote:
> Is this the same module that is in AOLserver CVS? Doesn't look
like it
> but they have the same name.
No, it isn't. I think that is one someone started many eons ago
and is
still "alpha". I think it needs replacing with something that is
maintained! :)
> One thing that might be useful is a way to provide storage
plugins for
> session data. If I could write a few routines, my_session_save and
That is a good idea, one I have thought about but didn't need and so
didn't implement.
But all operations are in an Ns_Set, so it doesn't matter where it
comes
from, as long as it is put into a set for getting/setting. So all the
implementation module would need to provide is GetSet(), SaveSet()
and
Destroy() functions. And maybe a "request done" function the trace
calls
so the memory cache your implementation would probably have can be
committed to the back end storage at the end of the request.
It could just be a loadable module that registers the functions to
call
with Ns_Session and overwrites the default ones.
One thing I would like is a small core change, it would be nice to
have
a simple char* in the NsConn struct to store the session ID,
rather than
my nasty request parameters hack.
Another slight performance improvement would be a pointer to the
cache
in NsServer, saving the find that is now needed on every access to
the
cache.
Cheers,
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave
the Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
