I don't know much about Cocoon, but anytime you have to parse and transform, it's going to take time. XML -> XSLT -> HTML is done a lot in the ASP world (I worked on such a project last summer) and the performance hit is very noticeable. XML is best suited for business-to-business communication between disparate systems.
Mark -----Original Message----- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 4:07 PM To: Struts Users Mailing List Subject: RE: xml-xslt v jsp I also posted a "what do you think about cocoon" question a week or so ago.....and still haven't gotten a response. I'm still waiting. JM > -----Original Message----- > From: Struts Newsgroup [mailto:@[EMAIL PROTECTED]] > Sent: Friday, May 10, 2002 3:55 PM > To: [EMAIL PROTECTED] > Subject: xml-xslt v jsp > > > Subject: xml-xslt v jsp > From: jisv <[EMAIL PROTECTED]> > === > Just wondering what people's thoughts are on using XML pages that > have XSLT > applied to them to display html pages rather than using JSP's. I read an > article recently that outlined this particular idea, apparently to even > more separate the business logic from presentation, and > supposedly increase > development time. I would have a couple of questions about how > performance > would differ, just how much quicker development time would be and simply > why this hasn't been implemented already, is there a flaw which > has stopped > such an implementation being used? > Thanks for your thoughts. > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
