[Zope] semipersistent

[Robin Becker]

In article <613145F79272D211914B0020AFF640191BF207@gandalf.digicool.com>
, Michel Pelletier <michel@digicool.com> writes
>
>
>> -----Original Message-----
>> From: Robin Becker [mailto:robin@jessikat.demon.co.uk]
>> Sent: Tuesday, July 06, 1999 12:01 PM
>> To: zope@zope.org
>> Subject: [Zope] semipersistent
>> 
>> 
>> I'm using various external methods to create GIF files in my current
>> server. These are expensive to produce, but are created on a per user
>> basis eg as the results of a user input.
>> 
>> How can I make these temporary in the sense that they live until the
>> connection is dropped.
>
>Hmm.. I wonder what you mean by 'connection is dropped'?  HTTP
>connections are stateless and immediately drop themselves upon
>completion.
>

>Do you mean to cache the images?  This would require writing your own
>Product with some trickery.  Also, it would be possible to write your
>own user folder which handled a 'session' and associated a certain
>object store (whether persistent or not) that lasted in memory as long
>as your session lasted.  This also would require some python.
>
ok I mean some kind of session idea on a per user basis. My current
implementation has a timeout based approach with the name of files being
hacked to include the client ip.

How would you suggest I approach this in Python/Zope?
>-Michel
>
>> -- 
>> Robin Becker
>> 
>> _______________________________________________
>> Zope maillist  -  Zope@zope.org
>> http://www.zope.org/mailman/listinfo/zope
>> 
>> (For developer-specific issues, use the companion list,
>> zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
>> 

-- 
Robin Becker