Diogo Souza da Silva - 2009-03-22 14:59:22 - In reply to message 1 from shariff
Do you want a suggestion about what service to build? Or about how restful services are?
I think any kind of message exchange service are nice to learn, as they are simple but can explore many resources. A service I built was for storing "Ideias" on "tags"(but in this one I was testing other framework and not used RestServer).
The most important thing in my opinion is to think about resources, for example a "message" can be resource, a "user", and you operate on the resources.
I if you have any ideia of service them tell here and I can help you on that.
Diogo Souza da Silva - 2009-03-24 01:32:25 - In reply to message 3 from shariff
I think I get it.
You will need to expose your data. Most of operation will be safe, using GET to retreive information. Leave operations that might result in changes on your data for later, start with the simple GET operations for read-only data.
You will need to define what informations will be available for consulting, them divide it into Resources. It really depends on how you divide your data. For example, if you work with places(shops, clinics, restaurants), the main resource would be, logicaly, "Place". Them define what will be exposed for this resource, as follow:
- GET /place -> List of categories, with links.
- GET /place/shops -> List of shops, with links.
- GET /place/shops/[id] -> Will give specific information of the shop identified by Id.
And maybe more complex, like:
- GET /place/restaurant/near-[postalcode]
Remenber to keep these operations read-only and initially don't offer data changes, with POST or others.
If later need of data changes operations can be allow with POST and PUT method with the need of http authentication, maybe even only on HTTPS.