@surya_s It's not published yet, but I'm sure @VaughnVernon knows what the final title will be :-)
1
Yes! RT @danwrong: Read about some of the stuff we've been doing to twitter.com: engineering.twitter.com/2012…
3
5
@MartijnLinssen But you know what? I have no enthusiasm spending any more time with this.
2
@MartijnLinssen Lame? So go on making unnecessary requests. I'm sure your system will be better.
@MartijnLinssen You might want to check what the HTTP spec actually says about caching
1
@MartijnLinssen It's stateless communication, i.e. request + resource state need to be sufficient, enhancing scalability
1
@MartijnLinssen In any distributed architecture, the best request is a request not made
@MartijnLinssen In case you're interested: infoq.com/articles/rest-intr… & infoq.com/articles/tilkov-re…
@MartijnLinssen You have to think of it like of a generic superclass
@MartijnLinssen 5) Code-on-demand (an optional aspect) means extending a client, not offering some privileges and then taking them away
@MartijnLinssen 4) You totally miss what Roy means with "stateless" in terms of REST, resulting in confusion about cacheability
@MartijnLinssen 3) "Cache prevents any means of scale" -- make sure you tell pretty much everybody on the Web about this
2
1
1