This sounds good to me as an initiative.
I am bit worried with the title apr (or is it acr?) since it overlaps a lot with apache httpd's apr (which is widespread in many distributions as one of the bases of httpd).

Wouldn't ajr be better a term since it's about a java binding?
Is tomcat native something really specific to apache httpd?
What about aprj or japr then?

paul


Le 04-avr.-09 à 09:21, Mladen Turk a écrit :

Hi all

This is not official project manifest, just few things
so I can gather info weather the project has any chance
to settle in the commons at the first place.

The project is completely different from other
commons projects, because it contains platform native
code beside java api.

The idea is to evolve the Tomcat Native to a
standalone component. It is used by Apache Tomcat
and Apache Mina projects, so we have two TLP
projects already using it.
And my plan is to use this component inside
daemons project for common platform tasks.

The java part will also have a special native
library dynamic runtime, allowing the native
module(s) to exist in the same jar and gets
extracted at runtime depending on the JVM platform
with all internal native dependencies resolved,
thus liberating the user from .dll hell.

So, thumbs up or down to pursue this, or do I
need to find a different settlement :)


Regards
--
^(TM)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to