RE: [Webware-discuss] Cache module

[Stefan S. <ste...@tu...>]

Hello Ian

On 1 Oct 2002, Ian Bicking wrote:
> > > Unfortunately, nobody answered my question regarding the best way to
> > > contribute the code. (If there was a problem with my original mail, I
> > > would like to know that problem. Was it that I mentioned the
> > > indentation by tabs? ;-) )
> >
> > I remember seeing the original email, I just forgot to respond.  The
> > standard way to add code to Webware is to upload a tarball to the Patches
> > page on the Webware SourceForge site, then send a message to webware-devel
> > describing the patch.  One of the Webware developers will eventually check
> > it in.  (Although it may take a while...)
>
> If it's not really meant to be part of Webware, but rather something to
> be used with Webware, then it could also go somewhere else (I don't have
> any problem with doing batteries-included with Webware, but it's
> probably easier to leave truly separate things separate -- I don't know
> where this caching module falls, though).

The caching module contains a single writer (updater) - multiple
reader cache as used in our project. The semantics of this cache is so
that the cache is only modified when no client uses it; i. e. from the
view of a client, the cache doesn't change while reading it. (Each
reader has to use a notify - release interface.)

> If you have a host, you can upload it there.  Otherwise you could try
> posting it as an attachment on the Wiki (webware.colorstudy.com --
> hmm..., the webware.sf.net/wiki redirect seems to be broken).  Once it's
> somewhere, you can make a link to it on the Wiki (just posting it the
> mailing list will make it hard to find later on, after all).

I've uploaded the code to

http://www.sschwarzer.net/download/multiple_reader_cache.py
http://www.sschwarzer.net/download/_test_multiple_reader_cache.py

It would be nice if someone looked at it. (I've done relatively little
multithreaded programming so far.)

I'm now working on a cache class with atomic access to individual
items and with a cleaner thread. If you already have such code, please
notify me to avoid unncessesary doubled efforts.

Stefan