- From: Fisher, Paul_K (Houston) <Paul_K_Fisher@bmc.com>
- Date: Wed, 26 Feb 2003 19:30:24 -0600
- To: "'eugene@datapower.com'" <eugene@datapower.com>
- Cc: xml-dist-app@w3.org, "'Laird A Popkin'" <laird@io.com>, "'Mark Baker'" <distobj@acm.org>
> From: Eugene Kuznetsov [mailto:eugene@datapower.com] > Sent: Wednesday, February 26, 2003 7:06 PM > > Well, what if I'm using synchronous SOAP+HTTP to deliver messages to a > disk-backed message queue? Should I use an HTTP-PUT then, since the > proximate destination is "storing to disk", to be followed, at a later > time, by processing? It really does not hinge on immediate or delayed processing aspect. You almost certainly did not intend for the "queue" to be one deep and for each HTTP-PUT to *replace* the previous one. HTTP-PUT encompasses the entire resource identified by the URI. HTTP-POST is much more inline with the "add to queue" semantic that you are looking to achieve. paul
Received on Wednesday, 26 February 2003 20:31:06 UTC