Hi folks,

I'm working on a team developing a Perl based web interface to a corporate
back-end that is exposed through a 'web-services-like' interface, ie we send
the back-end an XML formatted request (method name/paramaters etc)
and it produces an XML payload.

We're considering parsing the payload response into an XML/DOM tree,
inspecting it and modifying it (an element here, an attribute there) and
finally
pushing the result through an XSLT transform to produce the final web
output.

We have a prototype up and running using XML::LibXML and
XML::LibXSLT and had previously prototyped it using XML::DOM and
XML::Sablotron. Although we havent properly compared them yet it seems
(from notes/posts) that the XML::LibXSLT/libxslt approach may perform
better than the XML::Sabloton/Expat pairing.

Does anyone see any issues we might have with this handling of application
data entirtely in an XML tree from back-end to final rendering, rather than
application specific variable/data structures. This is a corporate
application
that will ultimately have many (~dozens-to-hundreds) concurrent users.

Would love to hear others experiences, and use of alternatives (AxKit,
other Libraries/platforms etc.)

--
cheers,
Dean Stringer
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
deeknow at pobox dot com [url]http://www.deeknow.com/[/url]