On Mon, 2004-06-21 at 16:02, Randall Smith wrote:
> This came out of a previous thread I started.  I'm using XMLRPC and I

> want to take advantage of Webware's session storage without using
> cookies.  What I have in mind is to generate a unique id, store and
> retrieve variables using that unique id.  Basically everything about
> sessions but the cookie.  I'll handle sending and receiving the
> unique
> id with the XMLRPC client.  Any idea how to do this with Webware's
> sessions?

Hi Randall,

It looks like you have a couple of options:

1. send a raw HTTP header from the client containing the _SID_ cookie value,
just as a browser would send it.  See WebKit/Application.py, and search for
'createSessionForTransaction'.

2. Use the 'UseAutomaticPathSessions' to encode the session id in the request
path.  See WebKit/HTTPRequest.py (search for _SID_)

Normally WebKit creates the session object the first time you access
the session.  The session object creates a random session ID for itself,
which gets sent to the browser (usually as a cookie).

In your case it sounds like each client machine will have a pre-assigned
session ID, so you'll need to create each session object and set the
identifier using the value received from the client.  So you'll need
to make a few changes in Application.createSessionForTransaction(),
and in WebKit/Session.py (to allow setting the identifier explicitly
instead of picking one randomly).

It should be quite workable; hope this gets you on the right track.

peace,
Jason

--
Jason D. Hildebrand
T: 204 775 1212
E: [EMAIL PROTECTED]



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to