jettero has asked for the wisdom of the Perl Monks concerning the following question:

My co-workers and I wish to provide access to our billing application via a set of carfully constructed XML command DTDs.

I've looked at a few packages on CPAN, and I've thought about a roll-your-own parser... It would use XML::Parser obviously, but felt like a traditional CGI rather than a mod_perl solution, which is dissapointing.

Well, currently the roll-your-own solution seems like it's the way to go. I want for these xml command documents to be gpg signed messages. I'm frustrated though, because I feel like there's probably a bunch of CPAN stuff out there, that already does what want... if only I could find it.

I looked at AxKit, it seems to be what I want, if only I could wrap my mind around it... I'm not very good with mod_perl yet though.

What is the best way to setup an xml command server that does gpg sigs and returns a response (in the form of another xml document)?

Replies are listed 'Best First'.
Re: XML Command Server
by bikeNomad (Priest) on Jul 16, 2001 at 21:24 UTC
    There's already lots of work that has been done on XML app server stuff. Look at SOAP and SOAP::Lite and XMLRPC::Lite. I'm not sure how signing would play into this scheme, although it seems that you may be able to sign it using a filter on the outgoing response.
      Oh, I was't very clear on that. The sigs are on the inbound xml to verify the identity of the entity submitting the command.

      Update: Looks like we're gonna have to decide to roll our own. SOAP doesn't seem to be anything we want, and I can't find this myserious XML::RPC (not that I have any idea what it is anyway). Anyhoo, I can't see any clear advantage of SOAP over use CGI; use XML::Parser; since that'll be a lot simpler. Well, unless anyone else has any other suggestions... I'm certainly open to it.