From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_JvOYNfL25l3DOSp7ooFhuw)" Message-id: <2BAAB6BE-154C-433E-8ECA-9FCA30A9EC11@mac.com> From: Pietro Gagliardi To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Date: Wed, 30 Jun 2010 15:54:43 -0400 References: <4C1F05E7-B327-480A-91F3-055076377C99@fastmail.fm> <3633bacf2efc9da1b911893b4029531b@coraid.com> Subject: Re: [9fans] xml Topicbox-Message-UUID: 3be6ff68-ead6-11e9-9d60-3106f5b1d025 --Boundary_(ID_JvOYNfL25l3DOSp7ooFhuw) Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-transfer-encoding: 7BIT On Jun 30, 2010, at 2:43 PM, ron minnich wrote: > as long as you don't care about the (observed) 100:1 ratio of XML glop > to data in, e.g., the Python XMLRPC stuff, it's great. Yep, I observed > that ratio when Xen made the cut to XML-RPC: 3000 bytes of RPC to send > 30 bytes of data. It's impressive: gigE gets reduced to 10 Mb ethernet > in no time; XML-RPC turns the network clock back by 20 years. A friend on AIM who I showed this quote to suggested XML should drop named close tags as a solution: stuff "C and Ratfor programmers find BEGIN and END bulky compared to { and }." - bwk --Boundary_(ID_JvOYNfL25l3DOSp7ooFhuw) Content-type: text/html; charset=US-ASCII Content-transfer-encoding: quoted-printable
On Jun 30, 2010, at = 2:43 PM, ron minnich wrote:
as long = as you don't care about the (observed) 100:1 ratio of XML glop
to = data in, e.g., the Python XMLRPC stuff, it's great. Yep, I = observed
that ratio when Xen made the cut to XML-RPC: 3000 bytes of = RPC to send
30 bytes of data. It's impressive: gigE gets reduced to = 10 Mb ethernet
in no time; XML-RPC turns the network clock back by 20 = years.

A friend on AIM who I showed = this quote to suggested XML should drop named close tags as a solution: = <tag>stuff</>

"C and Ratfor = programmers find BEGIN and END bulky compared to { and }." - = bwk

= --Boundary_(ID_JvOYNfL25l3DOSp7ooFhuw)--