Hi, <snip> >It is very unlikely that transformation will ever be your bottleneck anyway, >it's arguably the fastest part. Just how dynamic will your WS-style (REST?) >request will be? How (from a distance) will they be constructed? It looks to me >as though you might have a good use case for using a custom Provider, and that >as your DOM will likely be synthetic you'll be interested in the latest >get_dom() (currently only in CVS).
</snip> Robin, can you describe in brief what get_dom() will do? <snip> >> I am in the market for an app platform that doesn't have admitted >> memory leaks :o >Then one piece of advice (scarred by experience): pay very serious attention to >the versions of libxml2, libxslt, XML::LibXML, and XML::LibXSLT you use. If you >have a mix that works then stick to it until you *really* need to change. Those >are high quality packages but they have their tough bits and here and there >leaks are exposed that are triggered because of unpredicted interactions. Apart </snip> Just as a comment - I'm having memleak problems with XPathScript. I haven't heard anyone else complaining so I guess it has something to do with what Robin says (although LibXSLT works just fine, no memleaks there). Pavel
