search for: representational_state_transf

Hi, I am starting to learn rails and I went through the guide and a couple of tutorials. Even though I understand controllers or at least I can use them I can''t see yet the whole picture. Why do you need several controllers for a single application? If a controller is just a class whose methods interface with models and views, why not have a single controller for the whole application?

I need to split some information up between two servers, and wanted to use REST for it. I can write the REST server really easily...but I don''t know how I can actually use it. I downloaded Rails trunk to mess with ActiveResource, but it seems that it doesn''t have create functionality enabled yet. Is it possible to use AR fully? If not, what''s the best way to consume

Hi all We all know the model-controller-paradigm: I have a model "News" which has a corresponding CRUD-controller "NewsController". But now I''m quite unsure about the following... Guess we have normal visitors that visit our site www.??.com/news and we have administrators that create and modify news items. The admin should see an "Edit" link and a

...ces that which you''ve probably cursed at some point or other, the stateless protocol. Statelessness is why you''ve got to do all that extra work in your web applications to keep track of the state of the app for your users. Links to REST basics: http://en.wikipedia.org/wiki/Representational_State_Transfer http://66.102.7.104/search?q=cache:uCkFMHAh5b0J:naeblis.cx/rtomayko/ 2004/12/12/rest-to-my-wife+how+i+explained+rest+to+my+wife&hl=en http://rest.blueoxen.net/cgi-bin/wiki.pl?FrontPage In REST, resources (like files) are universally locatable via a common syntax. In HTTP this is done alm...