Ensuring compatibility between both ends of a JSON-based web service -
with xml-based web-services, clunky are, there's wsdl, schemas, dtds , other mechanisms describe data format , various tools various languages not handle marshalling , unmarshalling generate corresponding classes.
with json-based web services, marshalling , unmarshalling seem handled pretty well, when comes enforcing interface contracts can code , pray (or test , pray).
if you're developing both ends of web service in 2 different languages -- ruby , javascript, -- , domain complicated enough you're not willing deal lot of raw hashes, want code completion , error checking , whatnot -- seems option write necessary classes, hand, in both languages, , test hell out of make sure they're consistent both each other , json representations each 1 sending on wire.
are there tools make easier? of them worth using? or approach we're talking (i.e., matching class libraries on both sides) wrong begin with?
Comments
Post a Comment