HTTP is your architecture

HTTP is exciting stuff!

Although the talk had many interesting and valid points, I had trouble accepting the silly acronym and going to great lengths to explain it. It was obviously mostly a pun but the result was that the talk mixed http level and application level topics. Code generation or the fact that http can return JavaScript has absolutely nothing to do with the http protocol itself. 3 stars still for the quality of the covered topics.

Very well presented
The content was a little less interesting at some points, but they made some valid remarks and gave some very usefull info

Ivo, the "silly acronym" describes exactly what is behind HTTP 1.1. Roy Fielding (one of the principle authors of the specification) created this acronym to describe the network architecture that is realized by HTTP. And the "code on demand" part is also part of this specification. See here for reference: http://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch_styles.htm

Nice talk, very nice presented. I also enjoyed the talks from Tobias on DPC '11, so it was a reason for me to visit this one too :) (Ofcourse the subject also interested me)

After this talk I can confirm most of my apps don't speak HTTP...

Nice overview of the interesting parts of the HTTP spec

it was somehow enlighting how less we think about the underlying systems we use
the presentation itself was nice and clear and had a higher "entertainment level" than presentations delivererd by one person :p

I think that http is the new buzz of the year since Fabien Potencier put a hard work on it in symfony2 framework. But your talk was a little confusing and the only conclusion I got was that there is no solution to follow the rules dictated by the http rfc. Am I missing something ? Now that HTML 5 is in the place, and is the new standard everyone will or should use, how can we handle this ? No put, no delete, wtf ?

Anyway, I think you talked a little to much about http verbs (which we know don't fit in modern HTML) and maybe not enough about other important ( and working ) things like headers (cache for instance).

expected a bit more than just an overview of spl classes: more real world examples and insights.

awkward, the joind.in keeps the previous post.. anyway, nice talk but missed some focus.

Although I wasn't expecting too much from this talk, it really was an eye opener at some points. Very interesting talk. Very good speakers also. Good job!

Learned some new stuff, altough lots of it was confirming my experience with REST services already. But it can't hurt to refreshen knowledge about it. Thanks

Great talk, but I didn't like Kore Nordmann's english. He'll need to improve that.

Very interesting and on many points an eye opener. Problem is that kore and toby explained in detail what is wrong but no practical examples on how to make our apps utilize HTTP as it should.

Overall a very informative talk, I certainly heard some things that I wasn't expecting and certainly didn't know, that's why i'm coming to conferences, so thumbs up!

I agree with chrisramakers and mdekrijger. A lot of good info, in detail,

Missed some solutions to the real and practical problems you will face in trying to make your app according to the specs (eg login and large searches without post)

All in all nice talk!!

Well presented, you guys are a good speaker duo.
A few more practical would've been nice. Judging by some of the previous comments, there's still a lot of confusion about how to incorporate HTTP effectively in certain environments.

It was good, because it confirmed my current knowledge of HTTP (and REST), and i also learned some new things and got inspired.

Nice talk about the real basics of HTML (which almost never is used correctly :-) )

Well presented. I watched 3 of your talks and all of them were great. You two are a great duo.

I will (try to) apply the things learned in my next projects.

Nice combo presentation. Learned quite a few new things

Presentation was too much theoretical and does not provide real benefit for those developers that already have implemented REST interfaces.