On 02 Oct 2014, at 14:40, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2014-10-02 7:57 GMT-03:00 phil@highoctane.be <phil@highoctane.be>:
Too bad I live in a retared telecom-wise and mobile-competition wise country.
You're not alone.
Esteban A. Maringolo
ps: It is funny they use GET to send a message. :)
I was going to comment on that as well. For an action, the common REST practice dictates doing a POST. GET is to request the contents of something. Putting authentication in headers is also better, because it is more orthogonal. In full REST speak, you POST to a /sender resource which creates a new resource like /sms/123123 which you can then query for state (because it can take a while to determine success of failure) - this could also contain delivery timestamp, number of retries, proof of delivery and full contents for future/historic reference. Sven