Comments on: Eliminating web service dependencies with a language-specific abstraction barrier http://blog.cdleary.com/2009/04/eliminating-web-service-dependencies-with-a-language-specific-abstraction-barrier/ __author__ = 'Chris Leary' Mon, 06 Sep 2010 19:31:04 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: VaporWarning» Blog Archive » Deferred object models, plus caveat http://blog.cdleary.com/2009/04/eliminating-web-service-dependencies-with-a-language-specific-abstraction-barrier/comment-page-1/#comment-1150 VaporWarning» Blog Archive » Deferred object models, plus caveat Sat, 11 Jul 2009 19:02:17 +0000 http://blog.cdleary.com/?p=473#comment-1150 [...] say that you so happened to be eliminating web service dependencies with a language-specific abstraction barrier — using deferreds to represent your lazy data retrieval is a very nice abstraction. [*] /** * [...]

[...] say that you so happened to be eliminating web service dependencies with a language-specific abstraction barrier — using deferreds to represent your lazy data retrieval is a very nice abstraction. [*] /** * [...]

]]> By: Christopher Leary http://blog.cdleary.com/2009/04/eliminating-web-service-dependencies-with-a-language-specific-abstraction-barrier/comment-page-1/#comment-1072 Christopher Leary Sat, 25 Apr 2009 02:13:59 +0000 http://blog.cdleary.com/?p=473#comment-1072 Just thought of another good example: dates. Some APIs represent them in a string format for serialization, while others construct custom objects; however, no web service can use the *native* languages' data type in the payload unless such a thing is defined in the service's payload spec. (JSON has this issue.) Just thought of another good example: dates. Some APIs represent them in a string format for serialization, while others construct custom objects; however, no web service can use the *native* languages’ data type in the payload unless such a thing is defined in the service’s payload spec. (JSON has this issue.)

]]>