I'm developing an application which needs to update a remote database with certain data - is XML a good way of transferring this information? Would it be easy to create a program server-side to parse and decode this XML document into a usable form? Thanks, Huw Boy
Ajith Kallambella
Sheriff
Joined: Mar 17, 2000
Posts: 5781
posted
0
I think that is the right way to go. Consider the benefits of transferring data in an XML format back and forth from the server to client in an typical client-server scenario.
XML data is pure ascii text data and hence overheads of serialization and deserialization is minimal.
Any client can send the server the transaction data as an XML file, which means you can broaden your client base without doing physical (component) uploads on different machines. Deployment becomes a breeze. If the XML data server receives doesn't conform to standards( DTD/Schema, ) just ignore it!
Better than RMI - no need to supply all the clients with the class skeleton( and no need to update them too with later versions! )
A lot of component vendors are working on XML-DB frameworks and tools that will make this architecture even more workable. Sun already has JAXB - XML Databinding infrastructure that allows you to cook Java classes from the records in your DB result set and vice-versa. Hope that helps! ------------------ Ajith Kallambella M. Sun Certified Programmer for the Java�2 Platform. IBM Certified Developer - XML and Related Technologies, V1.
Open Group Certified Master IT Architect.
Sun Certified Architect(SCEA).
Kathy Shkarlet
Ranch Hand
Joined: Dec 01, 2000
Posts: 43
posted
0
Hi Ajith, I'm currently doing that - I use xml for client-server data and requests transfers - and my team fights me on the performance issues. Do you really think that xml beats serialization performance-wise? What about parsing time? Kathy
subject: XML -> communicating with a remote server.
0
