« The Code Room | Main | Autonomy, AI, and Memories of [Travises] »



Mark Baker
FWIW, I think CONNECT is good as it makes visible something that without which, wouldn't be; the tunneling of one protocol through another. Of course, the tunneled protocol's semantics aren't visible, but using CONNECT is like asking "Please may I tunnel?". It permits the server to say "No". And remember that REST is just a guide. When you really *do* need to tunnel, as above, it guides you to make that explicit in the messages, which CONNECT does. And yes, visibility is lost, at least to processors of the tunneling protocol. In many cases though, if a server permits a CONNECT to happen, it's because it understands the tunneled protocol - to whatever extent that's possible. I expect that what Roy's talking about in that slide is the that the simple secured-transport approach has won out for now (largely because it's simple, IMO), but we should consider the advantages of swinging back to message-oriented security. "Once you are inside the firewall, is the term "internet-scale" really material anymore?" Good question, but yes, I think it's still important. "Internet-scale" is another way of saying "supports unanticipated forms of integration", which is very good. The larger the company, the more important I think that is, since the higher the probability of unexpected things occuring. Of course, you don't have to get very big for that to happen, which is why I like starting with Internet-scale as my defacto position going into data-centric distributed app.

The comments to this entry are closed.

November 2008

Sun Mon Tue Wed Thu Fri Sat
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
Blog powered by Typepad

We Like