On Mar 1, 2007, at 12:12 PM, Drew Wilson wrote:
FWIW - JSON and SOAP are separate choices.
of course. but from the description, it seems like JSON might be an easier fit for the task.
When I identified this serialization as a problem here at work and commented that JSON::Syck is a much faster serializer (its written in C), someone in our group came up with notion of serializing results in JSON and then sending that back in a SOAP response ("envelope"). This workaround makes my skin crawl. Its a band-aid.
That sounds awful if you need those results in SOAP. but wrapping a JSON doc in SOAP for transport doesn't seem all that bad of an idea. SOAP is great for transport. JSON is great for interchange. At least thats what I think
// Jonathan Vanasco| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.