[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: REST has too many verbs

• To: <xml-dev@l...>
• Subject: RE: REST has too many verbs
• From: Bill de hÓra <dehora@e...>
• Date: Tue, 12 Feb 2002 15:13:46 -0000
• Importance: Normal
• In-reply-to: <NCBBKFMJCLIMOBIGKFMJGEPHHCAA.ldodds@i...>

> From: Leigh Dodds [mailto:ldodds@i...] 
> 
> End:
> 
> interface Gettable
> {
>   String get();
> }

End:

interface Gettable 
{
 String get(String what)
}


Or, 

interface Send
{
 String send(String verb, String noun)
}

interface Do
{
 String do(String verb, String noun)
}

interface Eval
{
 String eval(String verb, String noun)
}

[all the same, depends on what you want to call your VerbVerb ;)

You'll see this interface crop up again and again, though not always
with verb noun arguments. The method is often called invoke(),
service(), execute(), send(). Patterns like Command, Chain of
Responsibility and Strategy build on it. My understanding is that Simon
wouldn't always care about a return value and would probably expect the
calling process to return immediately in favour of a completion callback
or maybe a return ack as would people who prefer async messaging.
Pragmatically it's good to have blocking and non blocking versions:

interface Gettable 
{
 String get(String what)
 void   get(String what)
}



> I'm probably stretching the analogy way to far, but is it a case 
> of applying the same pattern but in a different context? 

I think so.

Bill de hÓra

• References:
  • RE: REST has too many verbs
    • From: "Leigh Dodds" <ldodds@i...>

• Prev by Date: RE: REST has too many verbs
• Next by Date: RE: commodity web
• Previous by thread: Re: REST has too many verbs
• Next by thread: Re: REST has too many verbs
• Index(es):
  • Date
  • Thread