William A. Rowe, Jr. wrote:
What sort of home should the apr project adopt, in order to leverage all theinteresting things that can be implemented as coherent apr packagelets?
My gut feel is this:APR should be the basic portability library, for individual functions that need to be made portable.
APR-util is for general package portability, with things like LDAP and XML that are almost portable but not quite, but that have general applicability across platforms.
APR-foo is for a specific feature, not general enough for the apr-util, but available for a specific package if necessary, and based on APR's structures and mechanisms (pools, etc).
Something that might be considered is for APR to grow into something along the lines of Java Commons, but for C.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
