[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] GZIP is an HTTP standard
>Uhh, XML database servers manipulate XML :-) What XML databases do internally is what gives them competitive advantage! A good XML database should be standards based, like XML via HTTP (preferably wrapped into your favorite languages API, like Java, C++, C#, perl, python, etc.) >It would be *nice* if there were open standard(s) for things like XML subsets that are easier to parse and/or alternative serializations of the infoset that are more efficient to exchange over standard protocols. I suspect that a lot of people are reinventing the same wheels, and it would be nice to see standards in this area. XML over HTTP 1.1 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html) with GZIP (RFC 1952 ). All are standard protocols, the compression is happening on the front end of your n-tier architecture from the web server itself (much less strain than running SSL), and the client surely has enough horsepower to unzip the payload, as time saved from the reduced transmission via slower connections (remember, wireless G3 is a whopping 144K). How do you think Web Services will ever work without all these middleware layers? Owen Walcher
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|