IMHO, what I suggested was not to replace APR or wrap it in whole, but having a loose couple integration model, that makes things easy in future, if in case.
For an example when IBM wanted httpd to run on later versions of AS400, they ported APR onto AS400 (forks from IBM would know this better than me), same as with HP when they wanted httpd on OpenVMS, which may not be our case though, I suppose?? So, if in case users of axis2c come across any incompatibility they would at least able to replace part of APR functionality with their own code, if a seamless migration model exist. Thanks -Lilantha -----Original Message----- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Thursday, September 29, 2005 2:58 AM To: Apache AXIS C Developers List Subject: Re: [Axis2] Guththila needs to define a set of error returns On Thu, 2005-09-29 at 12:08 +0600, Samisa Abeysinghe wrote: > Well going through the features supported by APR and also looking at the > next contender, NSPR > (http://www.mozilla.org/projects/nspr/reference/html/index.html) we > found that, if we are to support a portable runtimes in a pluggable way, > we would have to spend a whole lot of effort on the portable runtime > abstraction layer. > It would be almost like writing another portable runtime :( > > Hence IMHO it is the best to use only APR as a pre-requisit of Axis2C, > saves time and more relaible. > Also Apache httpd does it, why should we not? +1 .. we might want to consider making a layer for some stuff tho- for example, if inside PHP I imagine we have to use some PHP memory alloc routines rather than the APR one? So for some basic stuff we may indeed need to wrap APR but in general trying to wrap the entire virtual platform creates a new virtual virtual platform! Sanjiva. _______________ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
