On 5/19/06, Dan Creswell <[EMAIL PROTECTED]> wrote:
> Right, so GET is more generic but the result is that I can get back a
> much broader variety of information - How do I ensure I get back
> something I can actually process usefully?

How would you do it with getStockQuote?

Perhaps you could parameterize the invocation to describe what stock
quote format(s) you accepted;

getStockQuote( "FooStockQuoteFormat", "GOOG" );

You can do this with GET too;

GET http://www.example.org/quote/GOOG HTTP/1.1
Accept: application/FooStockQuoteFormat

> Am I not just coding at whatever level of abstraction suits me with
> whatever protocol suits me to transfer whatever suits me.  I can
> transfer using TCP and I can transfer with HTTP?

You cannot transfer with *just* TCP, you need a transfer layer on top
of TCP, which is what transfer protocols like HTTP, IMAP, SMTP
provide.

Mark.





SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to