Re: tcnative API stability/compatibility

2009-01-02 Thread William A. Rowe, Jr.
Mark Thomas wrote: > Rainer Jung wrote: >> Hi, >> >> we now have tcnative 1.1.x and trunk. What's our goal w.r.t. API stability? > > My understanding was that trunk was created to introduce APR 1.3 and > that the result would be tcnative 1.2.x. APR 1.3 is abi compatible to 1.2 - although you famo

Re: tcnative API stability/compatibility

2009-01-02 Thread Mladen Turk
Rainer Jung wrote: On 02.01.2009 11:57, Mladen Turk wrote: It doesn't mater if the API is stable or not. Tomcat will just depend on tomcat-native-1.xx.noarch.bin.zip and use the pre-compiled .jar (like any other jakarta-commons component for example) OK, I think that's exactly what I meant wi

Re: tcnative API stability/compatibility

2009-01-02 Thread Rainer Jung
On 02.01.2009 11:57, Mladen Turk wrote: Rainer Jung wrote: On 02.01.2009 08:25, Mladen Turk wrote: Rainer Jung wrote: a) bundling native and org/apache/tomcat/jni code in one place in svn and releasing together or b) separating only the native implementation Option a) was used cause we d

Re: tcnative API stability/compatibility

2009-01-02 Thread Mladen Turk
Rainer Jung wrote: On 02.01.2009 08:25, Mladen Turk wrote: Rainer Jung wrote: a) bundling native and org/apache/tomcat/jni code in one place in svn and releasing together or b) separating only the native implementation Option a) was used cause we didn't have separate tcnative release when

Re: tcnative API stability/compatibility

2009-01-02 Thread Rainer Jung
On 02.01.2009 08:25, Mladen Turk wrote: Rainer Jung wrote: a) bundling native and org/apache/tomcat/jni code in one place in svn and releasing together or b) separating only the native implementation Option a) was used cause we didn't have separate tcnative release when it was introduced.

Re: tcnative API stability/compatibility

2009-01-01 Thread Mladen Turk
Rainer Jung wrote: a) bundling native and org/apache/tomcat/jni code in one place in svn and releasing together or b) separating only the native implementation Option a) was used cause we didn't have separate tcnative release when it was introduced. Since this is now a separate downloadab

Re: tcnative API stability/compatibility

2009-01-01 Thread Rainer Jung
On 01.01.2009 18:15, Mark Thomas wrote: Rainer Jung wrote: Concerning the native side. What is the compatibility goal between the Java code and the native lib? Do we want to urge each using software to use a) exactly the same version of native, than the version of the Java code b) the same mino

Re: tcnative API stability/compatibility

2009-01-01 Thread Mark Thomas
Rainer Jung wrote: > Hi, > > we now have tcnative 1.1.x and trunk. What's our goal w.r.t. API stability? My understanding was that trunk was created to introduce APR 1.3 and that the result would be tcnative 1.2.x. > Citing from an earlier thread: >>> > we do have a 1.1.x branch in tcnative whic