If something like Ns_SetIGet exists, maybe use that, since headers are not case sensitive.
I know you were not trying to follow the cookie RFC's on this module, but maybe point that out so folks don't think that any cookie value will work as expected. Some chosen cookie values will screw up parsing of others, so you will get data dependent bugs showing up. There might be an issue with setting more than one cookie of the same name. Is it possible to update a set-cookie header? I chose to delete all cookies of the same name prior to creating a cookie. I'm not sure what the client behavior is when two cookies of the same name are received. What are the limitations of session data? For one they expire if the server restarts. I understand that this is by design in this case, but of course sessions which rely on persistent data will fail. I'm not sure I would call this behavior 'session', since it is really just a cache mechanism tied to a cookie. If this is not pointed out, users of other application servers may rely on this module providing sessions which persist for the expected time. tom jackson -- 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.
