On 6/14/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote: > A mixing of words. I was refering to the features that an API provides given > the amount of interface defined. GET/POST/PUT is the API. The parameters to > those operations are arbitrary.
Thanks for clarifying, but parameters aren't really arbitrary; they're rarely used on the Web, in fact. That's because most parameters in RPC styles like SOA are *identifying* information (e.g. "GOOG" in getStockQuote( "GOOG" )), and in REST, identifying information goes in the identifier to which the message is targetted. In other words, instead of; Message destination: http://example.org/stockQuotes/ Operation: getStockQuote Parameter: symbol=GOOG you use; Message destination: http://example.org/stockQuotes/GOOG Operation: GET Parameter: None HTTP headers are where non-identifying parameters go, but app-specific headers are very rarely used. Mark. ------------------------ Yahoo! Groups Sponsor --------------------~--> Everything you need is one click away. Make Yahoo! your home page now. http://us.click.yahoo.com/AHchtC/4FxNAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
