Comments on: I’m Cranky Because I’m Not Getting Enough REST

By: Eric

Eric — Tue, 25 Nov 2008 09:06:15 +0000

I think ultimately what bother you here is something not actually “resource”, like the “hide” action. It does not make sense to make them resourceful.

By: Pathfinder Development » A Look Back At Past Post

Pathfinder Development » A Look Back At Past Post — Fri, 03 Oct 2008 16:10:36 +0000

[...] REST [...]

By: masone

masone — Tue, 26 Aug 2008 07:06:06 +0000

I also think that Javascripts currently have no defined place in Rails. I recently was kind of annoyed by that fact. Why can’t we handle js.erb templates like we are using html templates?

My solution was a quick plugin which automatically includes the template in the file controller/action.js.erb (if existing). It’s nice because everything has a defined place, you can parse erb in your Javascript files and content and Javascript code are separated.

This does not solve all problems but maybe it helps you too?

http://github.com/masone/js.erb-auto-include-plugin/tree/master

By: Keenan Brock

Keenan Brock — Mon, 25 Aug 2008 23:18:09 +0000

You touched on a key point here. Rest is about accessibg resources. It isn’t about a granular client.

A word processor needs a document service to crud a document. But the front end does more stuff like spell checking. That is a client task not a document service thing.

So when you have a webapp and the client functionality is running on the server, things get confusing.

So separating the document restful service from the application/client/wordprocessor sounds great.

For some reason I was expecting to see flames though

By: Seban

Seban — Sat, 23 Aug 2008 08:59:35 +0000

I write my first RESTful project right now, but I don’t have problem descibed by you. I think this is not bad what you do. Probobly I will do the same.

By: Jonny

Jonny — Sat, 23 Aug 2008 00:11:59 +0000

What are your ajaxy things accessing when they make a call to the server? The way that I understand it, it would be fine to put all of those things on a page template without being unrestful. The point would be that you make them access the right resource when they do something on the server. Basically when you’re rendering your “index with a bunch of other stuff” page, you would consider those ajaxy things as just random html tags. Put them into a helper if the same thing will show up in a lot of different places. The restful part comes in when they actually do the ajaxy stuff, not when they are rendered.

Maybe it helps to think of a search box as just a more complicated link. If I’m on controller foo/index and I put a link to bar/index, that’s not being unrestful by any stretch of the imagination.

Does that make sense? I’m new to rest, so I’m still trying to think through a lot of these issues too.

By: Adam

Adam — Fri, 22 Aug 2008 21:16:15 +0000

I don’t have any real earth shattering revelation but I’ve always thought of it as dMVC (distributed MVC). That is, treat your RESTful data source(s) as nothing more than a model. Your HTML & most of the JavaScript is your View. The AJAX library is the controller (and there is some JavaScript that handles something like routing).

I’m not sure how that helps, but that’s how I do it.