I've looked on the web and here a stackoverflow. Don't see any good references that talk about url structure for rpc services.Coming from a REST perspective (or a 'single screen web page app'), if I have an entity that I want to expose actions upon, I just go {base}/entity and occasionally have to add ?action=something or '/action/something/ if the 'methods' go beyond CRUD, say 'search'.My feeling is that it's similar to that in RPC (json or xml), but I dod not find anyting to reference. Ideas, please?
What is a good rule of thumb for urls for rpc services
- Thread starter Fizcrync
- Start date