Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #8458
| From | jebblue <n@n.nnn> |
|---|---|
| Subject | Re: Low-latency alternative to Java Object Serialization |
| Newsgroups | comp.lang.java.programmer |
| References | <CAACD85F.81B3%bravegag@hotmail.com> <23089865.2265.1317485980290.JavaMail.geo-discussion-forums@preb19> <9ep735Fhr8U1@mid.individual.net> |
| Organization | Personal |
| Message-ID | <pZqdncl8QpHo9hrTnZ2dnUVZ_rGdnZ2d@giganews.com> (permalink) |
| Date | 2011-10-01 14:35 -0500 |
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 was a mistake, instead of coming up with an arcane hacked syntax to replace XML; JavaScript should have been improved to handle XML. -- // This is my opinion.
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
Low-latency alternative to Java Object Serialization Giovanni Azua <bravegag@hotmail.com> - 2011-10-01 14:46 +0200
Re: Low-latency alternative to Java Object Serialization Lew <lewbloch@gmail.com> - 2011-10-01 09:19 -0700
Re: Low-latency alternative to Java Object Serialization Robert Klemme <shortcutter@googlemail.com> - 2011-10-01 21:13 +0200
Re: Low-latency alternative to Java Object Serialization jebblue <n@n.nnn> - 2011-10-01 14:35 -0500
Re: Low-latency alternative to Java Object Serialization Robert Klemme <shortcutter@googlemail.com> - 2011-10-02 11:07 +0200
Re: Low-latency alternative to Java Object Serialization Roedy Green <see_website@mindprod.com.invalid> - 2011-10-03 11:43 -0700
Re: Low-latency alternative to Java Object Serialization Tom Anderson <twic@urchin.earth.li> - 2011-10-03 19:24 +0100
Re: Low-latency alternative to Java Object Serialization Roedy Green <see_website@mindprod.com.invalid> - 2011-10-04 02:45 -0700
Re: Low-latency alternative to Java Object Serialization Lew <lewbloch@gmail.com> - 2011-10-04 08:55 -0700
Re: Low-latency alternative to Java Object Serialization markspace <-@.> - 2011-10-01 09:48 -0700
Re: Low-latency alternative to Java Object Serialization Roedy Green <see_website@mindprod.com.invalid> - 2011-10-04 02:51 -0700
Re: Low-latency alternative to Java Object Serialization Robert Klemme <shortcutter@googlemail.com> - 2011-10-02 11:10 +0200
Re: Low-latency alternative to Java Object Serialization Tom Anderson <twic@urchin.earth.li> - 2011-10-03 19:15 +0100
Re: Low-latency alternative to Java Object Serialization Martin Gregorie <martin@address-in-sig.invalid> - 2011-10-02 11:50 +0000
csiph-web