|Subject||Re: Strategic Replacement for Services API|
> gbak?External process - somehow Java people do not like it.
> Or the dreaded services API (the admin server doesn't take it away).If that API going to stay - fine with me, then I shup up.
> Let me see if I understand this. You want to require every serviceThen application developer has to include and link to our library to
> module to be able to parse XML just in case you want to call it
> outside the infrastructure it was designed for?
> May I point out that if you're going to be calling the service
> modules, it would be a lot easier for you to build the XML parse
> tree directly (class Element in config) and skip the XML step
> altogether? Then neither of you have to parse XML.
build that tree.
Anyway, if Services API to make backup is going to stay, I'm ok with