RE: Reliable HTTP

Just read through the spec and primer.  One question jumps to mind though.
HTTPR looks like a mechanism for doing message queuing over HTTP in an
asymmetric manner.  That is, the client always has to initiate the
connection and the server always responds.  Do you envision this as the
default setup or do you also envision a network of peers where each client
is also a server and vice-versa?  If so, how does the message flow change?
I'd assume some of the intermerdiate polling (i.e. client issuing a PULL)
steps can be eliminated.


-----Original Message-----
From: []On Behalf Of
John Ibbotson
Sent: Monday, July 16, 2001 11:39 AM
Subject: Reliable HTTP

A recent thread on this list commented on the need for reliable delivery of
messages via HTTP. IBM has just released a first draft specification to
support reliability over HTTP. Together with a primer, it is available from
We welcome any comments and feedback on this specification.

XML Technology and Messaging,
IBM UK Ltd, Hursley Park,
Winchester, SO21 2JN

Tel: (work) +44 (0)1962 815188        (home) +44 (0)1722 781271
Fax: +44 (0)1962 816898
Notes Id: John Ibbotson/UK/IBM

Received on Monday, 16 July 2001 16:11:34 UTC