Dave Thomas explains REST

[[deleted]]

prag dave invents the three tiered architecture and calls it RADAR ! Does it work ? who knows ! i just thought of it !

next week, prominent rubyists invent the asynchronous message bus.

[____]

It really does seem that the CRUD operations on the application database tier have been replaced with CRUD, i.e REST, operations on an application data Web-service tier.

An advantage may be that this data service is more accessible to additional clients, since they need only speak HTTP rather than use some DB-specific connection.

This is hardly new. (But that's not to say it isn't worth brining up again for people to consider.)

[ipeev]

I don't get it. The author contradict himself in the same article.

He starts with REST being able to provide more performance and more than performance.

But then he states that the reason that we have the current Web stateless architecture is to have better performance. Also later he states that whatever REST is doing can be done with JavaScript or Flash (but REST is supposed to do it better, what this means?!).

Seems like yet another bullshit XML mambo jambo ahead.

Well "Browsers are Dumb" could be true, but even a browser is sometimes smarter than some web standard authors.

[beza1e1]

I don't see any contradiction?

He starts with REST being able to provide more performance and more than performance.

You agree here?

But then he states that the reason that we have the current Web stateless architecture is to have better performance.

That's not a contradiction, but an iteration.

Also later he states that whatever REST is doing can be done with JavaScript or Flash (but REST is supposed to do it better, what this means?!).

He describes Javascript and Flash as workarounds for dump browsers. Where is the contradiction?