RE: Providing a short name for single-request-response MEP

I can live with "request-response". 

Actually, one of the hidden assumptions in our use of this is that it is a 
reasonably rapid request/response.  If I'm placing an order and expecting 
a response in 3 months, this isnt' the one to use (or certainly the HTTP 
binding won't be happy.)  So, I'm a bit tempted to suggest something along 
the lines of "rapid-request-response", "request-with-immediate-response", 
or some such.  One day, we'll need a different pattern (or features to 
distinguish), long running from short running, IMO.    Again, I can live 
with "request-response".

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







"Henrik Frystyk Nielsen" <henrikn@microsoft.com>
Sent by: xml-dist-app-request@w3.org
04/22/2002 01:25 PM

 
        To:     "Christopher Ferris" <chris.ferris@sun.com>, "Williams, Stuart" 
<skw@hplb.hpl.hp.com>
        cc:     <xml-dist-app@w3.org>, "John Ibbotson" <john_ibbotson@uk.ibm.com>, 
<moreau@crf.canon.fr>, "Martin Gudgin" <martin.gudgin@btconnect.com>, 
"Marc Hadley" <marc.hadley@uk.sun.com>, (bcc: Noah 
Mendelsohn/Cambridge/IBM)
        Subject:        RE: Providing a short name for single-request-response MEP



I think that's fine

Henrik 

>request-response would work for me.
>
>Williams, Stuart wrote:
>
>>>what's wrong with simple-request-response

Received on Monday, 22 April 2002 20:26:54 UTC