Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #9712

Re: Low-latency alternative to Java Object Serialization

Show all headers | View raw

On 10/1/2011 3:35 PM, jebblue wrote:
> On Sat, 01 Oct 2011 21:13:40 +0200, Robert Klemme wrote:
>
>> On 10/01/2011 06:19 PM, Lew wrote:
>>> Giovanni Azua wrote:
>>>> I have this lite Client-Server framework based on Blocking IO using
>>>> classic java.net.* Sockets (must develop it myself for a grad course
>>>> project). The way I am using to pass data over the Sockets is via
>>>> Serialization i.e. ObjectOutputStream#writeObject(...) and
>>>> ObjectInputStream#readObject(...) I was wondering if anyone can
>>>> recommend a Serialization framework that would outperform the vanilla
>>>> Java default Serialization?
>>>>
>>> But you will be transmitting data via a format that omits the object
>>> graph overhead and focuses on just the data to share.  The object-graph
>>> knowledge is coded into the application and need not be transferred.
>>>
>>> XML is awesome for this kind of task.
>>
>> http://www.json.org/ might also be a good alternative which - depending
>> on format etc. - can be less verbose.  See http://json.org/example.html
>>
>
> JSON is convenient for JavaScript heads, it is not human readable,
> this is one reason why XML exists in the first place.

JSON is often more readable than XML for humans. You have the name
and the value and that is what you ned in most cases. XML with
heavy use of namespaces provide a lot of information for the
programs reading it, but for the human mind all that stuff is
more of a distraction from the essential.

Arne

Back to comp.lang.java.programmer | Previous | Next | Find similar

Thread

Re: Low-latency alternative to Java Object Serialization Arne Vajhøj <arne@vajhoej.dk> - 2011-11-06 19:59 -0500

csiph-web