John and Kenneth, You mention using a pluggable json library for the parsing but am I safe in assuming this means that the same library would be used to generate the json in ruote-rest / ruote-kit. We have run into some issues when pulling down json from ruote-rest with newlines being in the json string which causes some issues with the libraries we are using to parse them.
If this is the case, I am all for doing this (not necessarily the dependancy on ActiveSupport 3, but rather being able to use whichever json/xml libraries i like). My only other question is how you will manage to ensure compatibility between libraries. How would you ensure the calls you make to one parsing library are the same as other libraries that may have slightly different APIs? Nick On Fri, May 22, 2009 at 6:14 AM, John Mettraux <[email protected]>wrote: > > Hello Kenneth, > > well documented case ;) > > I'm not super happy with integrating ActiveSupport, there's lots of > things in there. But you are right, the newer versions seem promising. > > What I could do is simply stay away from JSON in the core ruote > classes so that people load their favourite JSON lib at will (like you > are doing for the amqp/xmpp participants). > > Only two core ruote classes do use JSON (and mostly for parsing). > > Same thing for XML parsing, I should avoid it in the core classes. > Pluggable XML library is sexy. > > So all in all, I guess "extras" classes can load active-support at > will. I will avoid it for the core engine (for instance, ruota has no > JSON/XML parsing at all). > > Is that "consensus" OK ? > > -- > John Mettraux - http://jmettraux.wordpress.com > > > > --~--~---------~--~----~------------~-------~--~----~ you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
