How about using 3rd-party JSON renderers ?
icylace - November 11, 2009 - 10:23
| Project: | JSON server |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
There are currently many issues related to the integrity of the JSON this module produces. Maybe it makes sense to scrap the original render code and just have users of the module install more robust 3rd party code. We could include instructions for installing a JSON plugin for jQuery (http://code.google.com/p/jquery-json/) to be used with Drupal.service() on the client side and some other library on the server side to account for when json_decode() isn't readily available. I'd be willing to submit a patch if there's interest.
#1
Icylace, I'm in favour of providing this patch, but for the rest_server module instead (it also supports json as input and output) and makes more sense. This module is a mix of json and rest functionalities, not being perfect in any of them. Could we move all the issues to the rest_server instead?
#2
So, does rest_server supersede json_server? How do they compare?