[wsf-c-dev] External dependencies
Samisa Abeysinghe
samisa at wso2.com
Thu Dec 7 06:45:34 PST 2006
James Clark wrote:
>>> - External dependencies. Which external libraries should we take a
>>> dependency on and how dependent should we be on them? libxml2 and curl
>>> are two obvious candidates.
>>>
>
> I should also mention openssl.
>
What about Guththila? Are we not interested in a pure pull model any
more? As far as I know, libxml2 is not the right choice for pull model.
>
> We should be aiming to maximize reuse. The way to create something
> really valuable with the minimum amount of work is to figure out the
> right things to reuse, and spend effort only writing stuff that really
> adds value beyond what is out there already. Rewriting everything from
> scratch is good, clean fun, but it's a poor way to create business
> value.
>
So this means that we should also look into reuse opportunities for
current Axis2/C implementation. So it compels me to assume that we would
more likely go down an evolution path rather than a revolution path.
> So from a platform integration perspective,
> it's important that our stack can efficiently accept a payload that is
> represented as a libxml2 DOM.
>
So does that mean that we would drop the current AXIOM only model for
the SOAP engine? Sounds to me that there would have to be DOM2AXIOM and
AXIOM2DOM converters in the SOAP engine itself. Is my understanding correct?
>
> In other words, I think we should be aiming for deep platform
> integration. Many open source programs work less well on Windows than
> on Linux. They behave like Linux programs ported to Windows and not
> like native Windows programs. Our goal should be to make our stack
> perform as well on Windows as a stack written to run on Windows
> exclusively, and similarly for Linux.
>
So eventually, we would have a considerable amount of code that would be
platform specific?
Samisa...
More information about the Wsf-c-dev
mailing list