On Sun, May 24, 2009 at 2:46 AM, Kenneth Kalmer <[email protected]>wrote:
> > >> Maybe a test reproducing the issue faced by Nicholas with JSON and >> newlines would keep away some surprises from us. What do you guys >> think ? >> > > Sounds like a good plan. I can roll a custom assertion into both ruote and > ruote-rest/kit to ensure the generated JSON doesn't have any newlines > characters. I'll check through the JSON specs as well, since I have to admit > I've relied blindly on the JSON being generated and parsed by same library > on both ends, which would obviously mask any issues like the one Nic has. > OK, I'll sleep on this one for the time being, but I have found a potential pitfall. Depending on how Nic calls ruote-rest, maybe the formatting of the response body can be interfering with the returned JSON [1]. Nic, is it possible you can copy out those lines in a problematic scenario and see if it makes any changes? Other than that is seems fine, all JSON encoding is now going through OpenWFE::Json.encode() which means it's an actual library bug that we'll have to report upstream Best [1] http://github.com/kennethkalmer/ruote-rest/blob/596017f17a11e5bac6ce4cdf0206a030546529c3/lib/inout.rb#L73-82 -- Kenneth Kalmer [email protected] http://opensourcery.co.za @kennethkalmer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
