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.