ROCA-style: Simple recommendations for decent Web application frontends

roca-style.org

14 points·obiefernandez··9 comments

ROCA strikes me as a very close description to an ideal Rails-based application. In fact, when Stefan was describing the pattern, I said "duh, that's a Rails app" or something like that. But what he's trying to do here is useful, introducing a description that is technology-agnostic.

The main deviation from ROCA in my own apps is that unless utterly simple to accomplish, I don't try to accommodate non-JS browsers. Not as a matter of principle but rather of convenience. It is nice to aspire to 100% functionality in non-JS contexts, even with degraded user experience. I just don't know that it's practical in most cases.

Out of interest, if you're not trying to accomodate non-JS browsers, what does your SEO solution look like?

I'm talking about internal pages that don't need to be spidered.

Fits my current ideals here: http://blogs.atlassian.com/2012/01/modern-principles-in-web-...

Finally a manifesto of REST principles :)

Please no :-) I'm really through with manifestos of any kind.

Some more details are here: http://www.innoq.com/blog/st/2012/03/announcing-roca/

"a set of rules to apply if the goal is to come up with a Web app that is actually on the Web as opposed to be tunnelled through the Web. We tried to come up with a catchy name, and finally arrived at ”ROCA”, a conveniently pronouncable acronym for “Resource-oriented client architecture”.

So rather than a manifesto, they're trying to devise a nomenclature, along the lines of how Ajax gave a name to non-page refresh server communication with the browser.

Nah, no way am I going to allow wget or curl to do application work.

Why not?

Reply on news.ycombinator.com