Re: How to monitor long-running fork in Skunkweb?

On Wed, Mar 09, 2005 at 09:06:14AM +0000, Andreas Kaempf wrote:
> Jacob, 
> 
> Can you tell us a little more about how you hand-roll your persistence
> mechanisms?  In particular, how do you detect which connection is
> calling in? Is CONNECTION.getSessionID() adequate, or do you
> recommend another way?

getSessionID() is only available when you are using the sessionhandler
service, so you can't use it otherwise.  But it is just a session
cookie; you can always plant one manually.

The alternatives to sessions are to store the data on the client
somehow, in javascript, perhaps, or to use a database that is less
generic than just storing pickles and do your own transaction
management.  I think the latter is the main thing that is different.

Every year or so I feel compelled to be curmudgeonly about sessions on
this list, and then soften up a bit and make some improvement to the
sessionHandler service, so perhaps this is just one of those times.  

I think sessions are definitely appropriate to use for a shopping
basket -- that's the paradigmatic use-case for them; the risk of
concurrency-related problems is relatively small and benign in that
case.  

> PS, I've used SkunkWeb's session mechanism for things such as the
> shopping basket in the Realm of Music site (see signature) and it seems
> to work great.

I like this!  http://realmofmusic.com/ goes to soundience, btw.

-- 
Jacob Smullyan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCLwhuuqamFyFXXLIRAu8mAKDIGhdfrfSOedFILoQphw6ax4dtggCfca8C
fOW69C28zOxZn7VMqLMyFpY=
=GyQ9
-----END PGP SIGNATURE-----