An online parts supplier is creating an XML-based application to deliver data to B2B suppliers and vendors, and also for use by B2C clients of various types. Which of the following provides the BEST design solution for the various clients consuming the XML data?
1)Use a single XSL stylesheet to transform XHTML1.1 linking to a CSS2 stylesheet for formatting. 2)Process the HTTP request and execute client-specific XSL transformations according to the client's capabilities. 3)Evaluate the client's needs based on the HTTP request and deliver formatted HTML to the client. 4)Deliver XML content to B2B clients and XHTML/HTML to B2C clients. 5)Pass XML directly to B2B clients, and use Active Server Pages or Java Server Pages to deliver customized HTML to B2C clients.
Hi here the answer seems to be 2. But i feel the answer should be 4. Somebody please explain this Micheal
My understanding is XSL Transformation is superior in some respect to JSP and is intended to replace it where appropriate.
Joined: Jan 08, 2001
Stara, where is connection between 4)Deliver XML content to B2B clients and XHTML/HTML to B2C clients. and JSP And I kind of disagree with superior. JSP if used properly (with MVC-Pattern, taglibs, JavaBeans and no scriptlets) is a very good technology for creating html content. Some people try XML/XSLT. Here is for example openSource framework to create struts where jsp is replaced by xslt. Does not convince me yet, but I haven't digged deep yet in that. capuccino.net See this XML/XSLT stuff more in backend. Friday one of my new collegues presented some new IBM product (forgot name) to integrate management of different user accounts (Windows, Sun, Oracle, what-ya-like) of an employee under one portal. This used xml heavily. You could also integrate the different user accounts to single sign on. just wanted to mention Axel
Joined: Nov 25, 2002
Hi Axel, How it could be 2, because how we can say the protocol is HTTP. From a mobile phone if i create a request, it wont be HTTP request right ? Micheal