Re: [Rails-devel] Rails-devel Digest, Vol 55, Issue 7

[Erik V. <eri...@xs...>]

I agree.

Erik.

 

From: kos petoussis [mailto:kos...@gm...] 
Sent: Saturday, June 09, 2012 10:39 AM
To: eri...@xs...
Subject: Fwd: Rails-devel Digest, Vol 55, Issue 7

 

about "Message 1": 
json is the modern way to go. You still will need to make objects that map
1:1 to the json representation, but it is not slow and readable.
If you have a backlog of xml, you can consider xstream.
http://xstream.codehaus.org/json-tutorial.html

gl,
kos

---------- Forwarded message ----------
From: <rai...@li...>
Date: 2012/6/8
Subject: Rails-devel Digest, Vol 55, Issue 7
To: rai...@li...


Send Rails-devel mailing list submissions to
       rai...@li...

To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.sourceforge.net/lists/listinfo/rails-devel
or, via email, send a message with subject or body 'help' to
       rai...@li...

You can reach the person managing the list at
       rai...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rails-devel digest..."


Today's Topics:

  1. Re: Another library to add? (Erik Vos)
  2. Re: Mocking library chosen (brett lentz)
  3. Re: Mocking library chosen (Stefan Frey)
  4. Re: Another library to add? (Stefan Frey)


----------------------------------------------------------------------

Message: 1
Date: Wed, 6 Jun 2012 22:47:21 +0200
From: "Erik Vos" <eri...@xs...>
Subject: Re: [Rails-devel] Another library to add?
To: "'Development list for Rails: an 18xx game'"
       <rai...@li...>
Message-ID: <001301cd4425$921dd600$b6598200$@xs4all.nl>
Content-Type: text/plain;       charset="US-ASCII"

What problems would this solve?

For initialization: it would be nice if XML data and objects were anywhere
near have a to 1:1 relationship, but in many cases that is far from being
the case.
So I suppose this would cause much rework.

For communication: I would tend to consider XML too verbose for such a
purpose.  It's not for nothing that (I believe) Google has invented a more
compact format.
And for all I know XML parsing and creation is slooow, but perhaps that is
due to the old libraries we now use?
Indeed we need something, but I can't provide much insight.
I had in mind something like uuencoded Serialized objects (the Java way),
but I suppose that is way too primitive for these days.
And of course it would be a big benefit if the transmission is readable.

Anyway, don't be put off by my (as usual) somewhat sceptical attitude.  I'm
way backwards in most of these matters.

Erik