On Jun 29, 2006, at 2:45 PM, Mark Baker wrote: > I understand. A lot of people think of HTTP as a transport, in large > part (IME) because it calls itself a "protocol"
I think part of the problem is that HTTP is so ubiquitous in most of todays IT work and at the same time appearantly so intuitively to understand. I have for years (including working as a Web developer) assumed I knew what HTP was because you see how it works and it is so simple. You do not need to look at a spec to make sense of it (partly because it is all text). I was unbelievably shocked when I actually read the specs (and Roy's thesis) and discovered that my undertsanding had been completely wrong all that time. As a side effect I immediately understood why there were sites on the Web I had allways liked because they just 'felt' right and sites I had allwas hated because the tended to get in the way somehow. The former ones were RESTful the latter ones weren't. It is indeed amazing how much deep thought went into gettiing HTTP 1.1 right - use it, build upon this effort! Jan ------------------------ Yahoo! Groups Sponsor --------------------~--> Something is new at Yahoo! Groups. Check out the enhanced email design. http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
