>From my own experiences, using XML data sources leads to poorer performance because of the parsing overhead, so I wouldn't suggest using them for large-scale projects. Producing XML output from your application, however, is extremely benefitial. For me, XML has acted as a universal templating engine; I produce XML which can be sent directly to a user, turned into HTML, a PDF, or just about any other format. You basically get a universal templating language. It will help make any site more accessible and portable. AxKit is nice for me because it isn't really language dependent and it can be used whether I'm coding in Perl, PHP, or Java.
Some questions to ask yourself: Does my site need to be portable? Do I want clear and efficient separation between concerns? (logic, presentation, etc) Do you think XML is really cool? Does the site need to scale well? Do you want your site to conform to standards? Doing this opens up a whole lot of possibilities etc etc Of course, XML is a mediary format for getting your data to other places - parsing and transforming may add some unwanted overhead to any project; however, if done properly, it can still be really fast :p I hope this helps you out a little bit... I think XML and XSLT are useful for just about everything, so my answers are a bit biased... I'd say axkit will serve your purpose, whatever it is. :P sebastian On Thu, 30 Sep 2004 14:58:13 +0100, Jon Hill <[EMAIL PROTECTED]> wrote: > Hi > > I have only just stumbled upon AxKit today and am very interested in what I > read. > > I mostly develop with PHP, I have a good grounding in XML and Perl also. I am > about to undertake a project which needs to be presented on Web browsers and > Mobile handsets (maybe others). I usually work with OOP techniques in PHP and > do what I can to decouple various layers from each other, relying on my own > APIs rather than template engines (so far). I am very keen to look more at > the possbilities that XML may give me to take this approach further. For > example I currently use XML to export content descriptions to third party > companies and I have knocked up a prototype Class that produces XML data from > the database and can be called over HTTP, I then simply parse the XML into > php data structures at the moment. > > Would someone be willing to help me work out if AxKit could be the tool I am > looking for. I like what I am doing with my prototype but I do need to think > about processing efficieny, scalability, and standards. > > What would be some of the key questions to ask myself before going down the > route of XML transformation? > > regards > > Jon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- ------------- [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
