HTTP Reliable Messaging
I have been studying Bill de Hora's HTTPLR Specification for Reliable Messaging using HTTP . All in all I think it's a great start to a somewhat complicated situation. It doesn't address issues like Once-and-only-Once delivery (as multiple clients could download the same message) or ordering of the messages. It does talk about reconciling the message deliveries between client and server, in both directions. The specification makes good use of the HTTP verbs and HTTP status codes, which I love. If they're there, and they apply, use 'em! I'm going to jump into my questions about the specification, so please bear with me. If you have the time, go ahead and read the specification. I'm a little concerned about the use of DELETE when reconciling message upload (as specified in section 8.3 ). The HTTP spec reads "The DELETE method requests that the origin server delete the resource identified by the Request-URI." To me, that says we're deleting ...