restful-architecture

So, I've been able to get restful controllers working with Route::controller('users','UserController'); class UserController extends BaseController { public function getAccount(){} } and so /users/account works. However if I try to do something like Route::any('account',array('as' => 'account','uses' => 'UserController@account')); and go to /account , it doesn't work ( NotFoundHTTPException ). Is there a way to use named routes and restful controllers in conjunction? I like how the restful system breaks up requests, and how named routes encapsulate the URI's and decouple them from the function

I have RESTful API within a web-service with some kind of resources like users, posts and so on. When I make request for list of posts (GET /posts), I want to retrieve array of posts only with reduced part of data for each post (i.e. subject, author name). When I make request for concrete post (GET /posts/42) I want to retrieve full list of post object fields, including big post body, additional info about likes count, comments count. I suppose it is exists many ways to solve this problem. In my mind, 3 most obvious are: Explicitly specify fields lits on every request (/posts?fileds=subject

A number of the developers here are having a friendly (some would say religious) discussion about whether a GET request from a RESTful API should return the ID of the requested resource . Let's assume the following GET request: http://my.api.com/rest/users/23 This currently returns: {"name": "Jim", "age": 40, "favoriteColor": "blue"} Note that "id" is missing from the result set. There are basically 4 camps battling with this issue. CAMP #1: When callers make the GET request, they already know the ID. Therefore, the result set should not include the ID. If callers need this data to enable UI

I'm looking for some direction in regards to the URI design for a RESTful API. I'm going to have several nested linked resources and have currently designed my URI's similar to this post: Hierarchical RESTful URL design The following example isn't what I'm building but I think illustrates my situation well. (Assume that a show can only belong to one network). /networks [GET,POST] /networks/{network_id} [GET,PUT] /networks/{network_id}/shows [GET,POST] /networks/{network_id}/shows/{show_id} [GET,PUT] /networks/{network_id}/shows/{show_id}/episodes [GET,POST] /networks/{network_id}/shows/{show

I am thinking about buildning a REST API with both websockets and http where I use websockets to tell the client that new data is available or provide the new data to the client directly. Here are some different ideas of how it could work: ws = websocket Idea A: David get all users with GET /users Jacob add a user with POST /users A ws message is sent to all clients with info that a new user exist David recive a message by ws and calls GET /users Idea B: David get all users with GET /users David register to get ws updates when a change is done to /users Jacob add a user with POST /users The

I want to provide different answers to the same question for different users, based on the access rights. I read this question: Excluding private data in RESTful response But I don't agree with the accepted answer, which states that you should provide both /people.xml and /unauthenticated/people.xml , since my understanding of REST is that a particular resource should live in a particular location, not several depending on how much of its information you're interested in. The system I'm designing is even more complicated than that one. Let's say that a user has created a number of circles of

I am trying to build a web application which should use Laravel as a RESTful backend API and AngularJS on client side. I read all the other post on Stackoverflow about the issue, but no one is definitely answering my doubts, at least, I did not find a definitive source example. For instance... Should I develop two completely distinct applications, a backend one with Laravel and another, purely client, with AngularJS? But in this case: how to handle them through a single domain (or virtual host)? Or should I create AngularJS templates inside Laravel, in the "views" folder and from them call

I'm building a RESTful API for a project I'm working on and I'd like to make the main application consume the API because: It will result in having one set of code to maintain Should we decide to expose the API for 3rd party devs it will already be done It opens up the possibility to make mobile applications that consume it I really want to learn how to do it The API will be hosted on a subdomain https://api.example.com and the main web application will be hosted at the root domain https://example.com . Conceptually I understand how everything works, but my main question is how the