Hi David,
I have another point I would like to add to the list: "do we have to
include it in the 'official' 3.3, or would it be better for it to be a
module ?"
Keep in mind that we have a relatively slow release cycle, and any feature
is adding more overhead for each release, and impose constraints on the
development of that feature itself ( because you have to sync with the
whole thing ).
I really want to keep each 'feature' in a separate module, if possible.
IMHO the whole nt-service should be packaged as a separate module and
released as such.
Of course, we never did that - and I'm sure your fix will have a good
impact on usability, so I'm +1 on including it in 3.3, but I would like
to start thinking in terms of modules...
Costin
On Mon, 10 Sep 2001, David Oxley wrote:
> Larry,
>
> I will have ironed out the final bugs by Wed/Thur and will submit the code
> for committing. Until then there is a patch for jk_nt_service that is
> complete, if that could be committed then the Service Manager could even be
> released separately. I have attached that patch. On your list of criteria:
> 1. It looks nice?!?! (Although it could do with better icons). Allows
> monitoring of local/remote Tomcat services.
> 2. It runs completely separate from TC. It just looks at the services.
> 3. As 2.
> 4. Sure I can do that.
> 5. I think it's fairly self explanatory. People used to Windows shouldn't
> have a problem. Plus I keep an eye on the list quite a bit so I can answer
> any queries.
> 6. I will get it ready for commit.
>
> Plus sorry for any duplicate messages. I had problems posting to the list :)
>
> Dave
> [EMAIL PROTECTED]
>
> -----Original Message-----
> From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
> Sent: 10 September 2001 16:08
> To: '[EMAIL PROTECTED]'
> Subject: RE: NT Service Manager
>
> Hi David,
>
> I'll be glad to consider it. My criteria for including a usability
> enhancement, prior to Release Candidate 2 is:
>
> 1. Offers a real benefit.
> 2. It's impact is *easy* to evaluate.
> 3. It won't impact the stability of Tomcat 3.3.
> 4. It is, or can be, sufficiently documented.
> 5. It won't generate more tomcat-user traffic than it's worth!
> 6. There is time to commit it.
>
> The last one may push some desirable features into a later
> Tomcat 3.3 release, which I expect will happen. Tomcat 3.3
> can't release unless there are enough committers to continue
> support. I'm still willing to consider simple usability
> enhancements, time permitting :-), and not rule them out absolutely
> at this point.
>
> Cheers,
> Larry
>
> > -----Original Message-----
> > From: David Oxley [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 10, 2001 10:18 AM
> > To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> > Subject: NT Service Manager
> >
> >
> > Larry and all,
> >
> > I am writing a service manager based on the UI of SQLServer's Service
> > Manager. It is nearly finished and I am aiming to finish it before the
> > release of TC3.3. If anyone is interested in this, please
> > give it a go and
> > give me some feedback. Larry, is it to late for TC3.3 (assuming you're
> > interested in it anyway!).
> >
> > I have attached the current source code. It relies on an
> > updated version of
> > jk_nt_service.exe for which I have also supplied a patch. I
> > will be doing a
> > patch to get it working for TC4, but as TC4rc1 is out it is
> > probably to late
> > for that.
> >
> > Both attachments are in service.zip.
> >
> > If anyone wants me to send them the binaries, just say. I
> > think it's too big
> > for the list.
> >
> > Thanks.
> > Dave.
> > [EMAIL PROTECTED]
> >
> >
> >
> >
>
>
ntservice.diff
