Could someone who is advanced enough to know about REST stuff please explain this to me.
From what I understand, if I had a data store, and I setup a REST Server (REST API), then any HTTP client could consume my service.
Assume INTERNAL USE at a company - not for public use.
So, if I want to publish purchase history information, based on a supplied Serial #, then I could do 3 things.
(Client would be a smartphone or tablet)
1) Existing Aware IM to login and go to search screen and see result. Enter the serial # and then show the purchase history. This prolly shows confidential Customer name, etc. info which is why this can't be public.
2) Use Aware IM Mobile option (additional fee) to have "mobile" screens, but basically the same functionality.
3) Assuming Aware had REST working to this level, allow any browser screen to supply the serial #, and similarly, show the purchase history. No Aware needed at the client - just a webform that sent a request.
For case # 3, I'd still want to authenticate somehow so only auth. users can use this. But whats "the big deal" about REST in THIS CASE? I don't see the advantage of REST over just logging in to the web app.
Feel free to offer how a REST API to provide similar functionality is advantageous.
Maybe IN MY LIMITED USE CASE, the REST API isn't the way to go, so help me understand a modified business case where REST would be awesome.
thx
jaymer...
