Re: [Webware-discuss] Deprecating OneShot.cgi

[Tim R. <ti...@pr...>]

On Wed, 30 Oct 2002 16:38:41 -0600, Ian Bicking <ia...@co...>
>
>I posted a question about this to the -devel list, but to finalize it --
>does anyone object if OneShot is deprecated?  The auto-reload feature
>just added to CVS is vastly superior in all ways, IMHO.  OneShot is a
>source of bugs, strange corner cases, and confusion to new users.
>
>If deprecated, I will take all mention of it out of the docs, take it
>out of MakeAppWorkDir.py, and put a warning message at the top of the
>file, but OneShot will remain around in body if not in spirit, at least
>for 0.8.

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.

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".  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, but I think it's a little early to yank OneShot out of the docs.  
Why don't we target that for 0.9?

By the way, numerologists in the group should be amused by the subject line 
of the most recent digest, quoted here:

  Subject:  Webware-discuss digest, Vol 1 #1111 - 11 msgs

My only regret is that it came out one day before 11/1...

--
- Tim Roberts, ti...@pr...
  Providenza & Boekelheide, Inc.