Personally i loved the 'json in header' feature, it allowed me to have
large quantities of html in the responce body, and some params, or other
divs to update, etc in the x-json header ..
I assume by large quantities of HTML you mean just 1 large quantity of HTML? With more than one large quantity of HTML, it seems a cleaner design to have them all in JSON and have the entire JSON string in the response body.
The JSON vs. response body design seems to encourage putting HTML in the response body which is designed to hold a single HTML fragment. You can still put other HTML fragments in JSON but IMO it seems cleaner to put them all in JSON instead of fragment 1 in the response body and fragments 2-n in JSON.
Worked out much better then having to xml parse the responce body into
sepperate entities :-) (like openrico.org does forinstance)
The comparison should be JSON in X-JSON with separate response body vs. JSON in response body. You seem to be comparing JSON in X-JSON with separate response body with XML in response body. JSON uses _javascript_'s eval, not xml parse, so if Rico uses XML it's probably not a good comparison.
John
_______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
