Craig R. McClanahan at [EMAIL PROTECTED] wrote:
>
> So far, commons is 100% Java, but I don't believe they (really we, cause
> I'm a committer there :-) would be opposed to a commonly useful project
> that has native code components.
Dunno...
>> jakarta-tomcat-connectors is a place where C and Java are mixed ;-)
>> What about jakarta-tomcat-connectors/service?
>
> Except for the fact that it's not a connector, and has nothing really to
> do with Tomcat :-)
Exactly...
> If we stay under Tomcat auspices, I'd vote for jakarta-tomcat-service
> instead.
I'd say, let's stick it with Tomcat until we don't have a "proof-of-concept"
that it works, and then we can decide... I like jakarta-tomcat-service.
Pier
- Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- Re: Separating Service code from Tomcat 4.0 Craig R. McClanahan
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- Re: Separating Service code from Tomcat 4... jean-frederic clere
- Re: Separating Service code from Tomc... Craig R. McClanahan
- Re: Separating Service code from... Pier P. Fumagalli
- Re: Separating Service code ... Pier P. Fumagalli
- Re: Separating Service c... Craig R. McClanahan
- Re: Separating Service c... Joe Flowers
- Re: Separating Service c... Pier P. Fumagalli
- Re: Separating Service c... Pier P. Fumagalli
- Re: Separating Service c... Remy Maucherat
- Re: Separating Service c... jean-frederic clere
- Re: Separating Service c... Pier P. Fumagalli
- Re: Separating Service c... Andy Armstrong
- Re: Separating Service code from Tomcat 4.0 jean-frederic clere
