Hey,
In my latest Apache::ASP dev version .18, I have
2 implementations of how a developer can manage cookieless
sessions, which I have worked out with Serge Sozonoff
and Remi Fasol.
The coolest extension is where if SessionQueryParse
is set, the HTML buffer, with buffering enabled, will be
parsed for links, and the session-id automatically
inserted into the query string, which will be scanned
for the session-id on startup. Only local links will
be parsed unless SessionQueryParseMatch is set to specify
a regexp on which to match for parsing URLs.
So a link like <a href=page.asp> would become automatically
<a href=page.asp?session-id=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa>
for the first page of a user's session, and all pages for
users without cookies enabled. The first page for even
cookiefied users gets this because the browser does not yet
have the session cookie set.
The process will not occur if a session-id cookie is
detected, so the runtime performance hit will only
apply to users without cookies. A more efficient method
of doing this, but less developer friendly is when
SessionQuery is set, and the $Server->URL() extension
is used to generated a URL with session-id parsed in,
that can then be inserted like in
<%= $Server->URL('page.asp') %>
This is a real light-weight option, and won't slow things
down much, because only the URL is being parsed, instead
of the whole content buffer. But for those of you who
are lazy, and don't want to do this to a whole site,
the SessionQueryParse is a great option.
So, if anyone would like to try this before its ships
out for general consumption, that would be great. Send
me a mail, and I'll send you back my dev version.
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
