On Tue, January 13, 2009 5:55 pm, Paul McNett wrote: > MB Software Solutions General Account wrote: > >> On Tue, January 13, 2009 4:38 pm, Geoff Flight wrote: >> >>> Never having really written such an app Ive still wondered why you >>> would use XML vs binary. Why would you use a verbose data description >>> in a situation where bandwidth is relatively limited? That said, I now >>> need to write a web service and that has convinced me to use binary >>> and not XML. Everyone raves >>> over XML and frankly, I don't get it. IN a closed architecture I see >>> no point at all. >> >> >> You've kinda answered your own question: in a closed architecture, >> it's overkill. You binary in your closed architecture. XML is good >> where you have to play with others in the sandbox OUTSIDE of your >> architecture. > > XML is a storage format, convenient because it is human and machine > readable and editable. But the first thing you should do when working with > an XML format file is to convert the relevant parts to a native data > structure, and only convert it back to XML when saving back to disk. > > > When working with web services that expect XML, you have to comply, > obviously, but if you are controlling both ends don't use XML, at least > without compressing: it is overkill and wasteful of resources.
Right. Closed-architecture where it's your football and your rules: use binary. Where you must play with others under neutral rules: XML. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
