IMHO, entering a patch is fine. Before our next release we'll review both
the open bugs and open patches.
Speaking of a next release, does anyone want to be a release manager for an
0.8 release? It's been so long since our last release that I think we
should cut one soon, even though there are s
Geoff,
What is involved in being a "release manager" in your opinion? And
what qualifications does one need?
-Stuart-
Geoffrey Talvola wrote:
IMHO, entering a patch is fine. Before our next release we'll review both
the open bugs and open patches.
Speaking of a next release, does anyon
Here are the basic release procedures from the 0.7 documentation:
http://webware.sourceforge.net/Webware-0.7/Docs/ReleaseProcedures.html
As far as qualifications, you should probably be a Linux/Unix developer and
you should have some familiarity with CVS, tools like tar, and Webware. You
do NOT n
So what is the status of NewThreadedAppServer?
Is this still intended to replace ThreadedAppServer?
I noticed that the "stop" function does not work when invoked through
main() because AppServer.stop() does not take named arguments.
-Stuart-
On Fri, 2002-12-13 at 19:23, Stuart Donaldson wrote:
> So what is the status of NewThreadedAppServer?
>
> Is this still intended to replace ThreadedAppServer?
I'd like it to. I haven't heard much opinion on it and it would be nice
to get it tested better -- I think Goeff tested it a bit on Windo
I am working out the details of a patch I discussed about a month ago
that would allow the ThreadedAppServer to be subclassed, and I wanted to
bounce the ideas out on the list before I was finished to see if there
was any further feedback or interest. My goal would be of course to see
this get
Ok, I'll start using NewThreadedAppServer for my work as well.
If I get my Subclassing patch done and accepted, it might be an
acceptable way to add the new monitoring methodology to a
ThreadedAppServer.
You could have a MonitoredAppServer class which subclasses
ThreadedAppServer and adds th
I have noticed a couple of places where New and Old are used to identify
improved and out-dated methodologies.
NewThreadedAppServer, serverSideInfoForRequestNew and
filenamesForBaseNameNew
Is the plan to remove (at least the New*) names prior to the next
release? If not, I would encourage it.
