On Sat, Feb 01, 2003 at 01:25:08PM -0500, S Woodside wrote: > I didn't say disappear XPS, just discourage it. People who approach > AxKit for the first time shouldn't see XPS. It's an ASP solution and > AxKit isn't an ASP system.
My reasons for not really adopting the XPS approach are: - it's not standard, so if I'm forced to move the project to let's say Java, I would need to rewrite it; - it cannot be processed on the client, so I do not see it as something that would take load off my servers eventually; - and I do not like it's mixing code and markup, but that's not as important. XLST, even if it is more complex a complicated and so on, is standard. So any effort put into building large site on XSLT promises to be living for some time to come, even if requirements or the management changes. And, MSIE and Galeon seem pretty fine in processing XSLT. So I would agree with the OP (and maybe rephrase the wish): could we promote AxKit more as a an environment for the industry standard way of doing XML processing (which would be XSLT nowadays), _also_ including Perl-specific ways of getting the task done, like XPathScript? When I mentioned AxKit to my colleagues, they mostly answered "yeah, that's the Perl-only tool", and I had to go to to some length of explaining that no, you can do XSLT easily and reasonably, _and_ you can also use XPS quick lightweight processing. -- ------------------------------------------------------------------------ Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/ ... all of these signs saying sorry but we're closed ... ------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
