From: Geoffrey T. <gta...@na...> - 2002-10-01 14:37:58
|
Stefan Schwarzer wrote: > On Tue, 24 Sep 2002, Matthew J. Feifarek wrote: > > >On Tue, 10 Sep 2002, Stefan Schwarzer wrote: > > > > > >I now have a cache module, together with a unit test. For use in a > > >application class I coded a (hopefully thread-safe) "single > > >updater/multiple reader" cache which I'll extend/modify as > we proceed > > >in our project. > > > > > Did you find a way to share your code? I'd love to see it. > > 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...) Or, if you'd like to get Webware CVS write access yourself, that can be arranged, too. See http://webware.colorstudy.net/twiki/bin/view/Webware/DeveloperGuidelines . - Geoff |
From: Ian B. <ia...@co...> - 2002-10-01 21:14:08
|
On Tue, 2002-10-01 at 09:37, Geoffrey Talvola wrote: > Stefan Schwarzer wrote: > > On Tue, 24 Sep 2002, Matthew J. Feifarek wrote: > > > >On Tue, 10 Sep 2002, Stefan Schwarzer wrote: > > > > > > > >I now have a cache module, together with a unit test. For use in a > > > >application class I coded a (hopefully thread-safe) "single > > > >updater/multiple reader" cache which I'll extend/modify as > > we proceed > > > >in our project. > > > > > > > Did you find a way to share your code? I'd love to see it. > > > > 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). 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). There's also http://webware.sourceforge.net/ThirdParty.shtml , which could link to it. I think we should move that to the Wiki, though, so it's easier to keep up-to-date, and then link to it from webware.sf.net. Ian |
From: Stefan S. <ste...@tu...> - 2002-10-02 13:55:54
|
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 |