I delivered a project for pay on a box that I had NO control over.
OneShot was the ONLY way that I could get it working. Because the box
was fast and the traffic was fairly low, it worked like a charm.
I believe OneShot is still useful for this purpose.
I have to veto the "deprecation" because if we deprecate it, then new
developments will break it, and it will also be forgotten about in the
Regarding the newbie problems, we can now direct them to use the
auto-reload feature, and also point out that OneShot is extremely slow
and a last resort.
On Thursday 31 October 2002 11:43 am, Ian Bicking wrote:
> On Thu, 2002-10-31 at 12:43, Tim Roberts wrote:
> > My feelings are not particularly strong, but I wonder if we
> > shouldn't let the auto-reload code age for more than a week before
> > we kill OneShot. I don't think anyone is willing to certify the
> > auto-reload code as "bug free", or even to certify that it has
> > fewer bugs that OneShot: we just haven't had the experience.
> The real reason I brought up the deprecation for right now isn't
> because of auto-reload, but because I'm going through documentation
> and don't want to spend time documenting things I don't think people
> should use. Plus looking at documentation reminds me of things that
> exist that I'd forgotten about (like CGIWrapper).
> > I use OneShot.cgi for development work because it gives me the
> > perception of lower complexity, as well as lower impact on a
> > lightly used web site. I know that each page runs with a "clean
> > slate".
> This is part of why I think OneShot should be deprecated -- it
> presents a different environment than you'd find in a running site.
> The development environment should be as close to the production
> environment as practically possible.
> I guess I've always thought OneShot was a hack, and it's not so much
> that auto-reload is a sure-fire replacement, but that OneShot has
> needed to go for a long time and auto-reload finally offers a
> Deprecating OneShot means experienced users will still have access to
> OneShot, but new users won't know it exists. I think a lot of new
> users either get the false impression that Webware is really slow
> because of OneShot, or that they can run it in a pure CGI environment
> using OneShot (i.e., your typical commercial host). Hopefully we can
> actually remove OneShot when auto-reload has been tested more, which
> will probably be after 0.8 -- it's the new-user experience that this
> level of deprecation is directed at.
> > I haven't tried the auto-reload
> > feature (and I suspect very few of us have), so I don't know how I
> > will feel about it
> Try it, I think you'll find it very pleasant.
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> Webware-discuss mailing list