Hi John, > The choice of HTTP in our > requirements comes about from customer feedback. In spite of the > deficiencies of HTTP, it is the de-facto infrastructure on the Web and > adding reliability to it is seen as important. I don't disagree that reliability is important, but assuming that HTTP is a transport protocol is a very easy way to do the wrong thing with it. HTTP defines an application model, which much more narrowly constrains how reliability fits in than is the case with a transport protocol. Both HTTPR and the requirements draft do not respect this model. For more on this, see; http://internet.conveyor.com/RESTwiki/moin.cgi/RestArchitecturalStyle MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.comReceived on Friday, 23 November 2001 15:33:30 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 March 2006 20:11:29 GMT