================================================ Q 23.An online travel agent company wants to create an XML-based application. Company interacts with its B2B partners and supply better travel-package deals and airfares. It also does business by interacting same information directly with consumers and B2C clients of various types through it's own website. Which of the following provides the BEST design solution for the various clients consuming the XML data?
For B2B requests, application will serve XML . The requesting clients may transform the XML into its own vocabulary using XSL stylesheets.
For all requests write single XSL stylesheet to transform XML into XHTML.
Application may evaluate the request to decide whether the client is B2B or B2C.
For B2B requests, application will transform its XML into the requesting clients XML vocabulary using XSL stylesheets and then serve it.
For B2C requests, application will transform its XML into HTML using XSL stylesheets and will serve it. ================================================= Can someone please explain what is the exact difference b/w a B2B and B2C clients and what should be our considerations in serving them with XML/HTML info. Also when it comes to stylesheets, how does it change as to where they get applied to the information (either on the client or the server). Are there any good links which explains these kinds of processes? Thanks.
B2B refers to businesses being held between 2 or more companies and B2C refers to business between an organization and clients. When a client orders something from internet,for eg: buys a book from amazon,then this scenario is B2C.However if amazon requests the supply of the book from one of its distributors,then this scenario would be B2B. Similarly a C2C scenario would be when clients interact with clients,ie may be in an auction site where they bid on products. A client may use a web browser or any hand held devices to access a web site,which restricts that only HTML should not be provided to the client. So depending on the type of client,the server may decide to transform its XML data,and provide it to the client or may provide both the XML data and the XSLT to the client and processing may occur on the client end. Memory considerations is another reason for deciding whether client side or server side processing would be done.
Hi Jayadev, As Vasudha has pointed out, internet transactions are generally B2B and B2C (C2C is also one rare phenomenon). Whenever it is B2B (Business to Business), the data processing is performed mostly by the systems with no or very less of human intervension. For eg: in a company A which assembles computers, it raises a Purchase Order when it's stock of monitors comes down a threshold point. The vendor (supplier) receives the request and starts manufacturing the pasrts for A, does the QA, packages it and delivers it. All this happens as a sequence when the stock level goes down. Here all operations are performed by your computer n/w and manufacturing system. This is a pure B2B scenario. In case of B2C (Business to Customer), the other end could be a human being who raises a request. The customer could be a single unique entity too who triggers an action. I hope this helps. Good luck, Rakesh. ----------------------- IBM Certified Developer -XML and related technologies
posted 17 years ago
Rakesh and Vasudha, Thanks a lot for the clarification. When it comes to applying the stylesheets stuff ......... ================================================= 1) for B2B client, i think we prefer sending it the raw XML and expect him to do the transformation by himself. Is that right? If the client memory footprint is a consideration( i guess this means that there is shortage of resources on the client side), we tend to do the client-specific xsl transformation on the server itself and then send it the transformed xml. Please correct me for mistakes here. 2) for B2C client, the client will generally be a browser (as opposed to a process as B2B), and we transform xml and send them HTML. The above stuff are things i learnt the hard way by taking different tests Where does XHTML fit in the above scheme of things? ================================================= Previously i asked guys as to pin-point the prevailing conditions for using DOM/SAX/XSLT. Can any one do this please?? ================================================= Thanks.
Hi jayadev, When we are using B2B the common mode of transfer will be xml file When we are using B2C/C2C we have to convert the xml file and render it depending on the client(browser pda etc...)
There are three ways where we can render it. 1. Convert it in the server and render to client 2. Convert it on the Client 3. Convert into HTML before placing in on the server. If memory constaint is not a problem means we can do the conversion in client else we have to do it in server. So, my choice to ur question will be choice a..(pls correct if iam wrong) All other guys explained B2B and B2C.... [ October 03, 2002: Message edited by: Vasan ]
Rototillers convert rich soil into dirt. Please note that this tiny ad is not a rototiller:
Two software engineers solve most of the world's problems in one K&R sized book