Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Low-latency alternative to Java Object Serialization Date: Tue, 04 Oct 2011 02:45:19 -0700 Organization: Canadian Mind Products Lines: 27 Message-ID: References: <23089865.2265.1317485980290.JavaMail.geo-discussion-forums@preb19> Reply-To: Roedy Green NNTP-Posting-Host: RCd/Ul4tyxGUBII8WGwa5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8513 On Mon, 3 Oct 2011 19:24:20 +0100, Tom Anderson wrote, quoted or indirectly quoted someone who said : >Specifically, i believe >that: (a) developing an XML-based transfer format using JAXB will take >considerably more effort than using standard serialization Serialisation handles complex data structures, even loops. XML is limited to trees. Serialisation handles any imaginable data type without extra work. XML requires inventing an external character representation and a way of converting to chars and back. Serialisation is hard to upgrade. XML is easy. Serialisation pretty much requires everyone to stay in sync with identical software. XML allows clients with out of date software, software in other languages, or even no software at all. -- Roedy Green Canadian Mind Products http://mindprod.com It should not be considered an error when the user starts something already started or stops something already stopped. This applies to browsers, services, editors... It is inexcusable to punish the user by requiring some elaborate sequence to atone, e.g. open the task editor, find and kill some processes.