Re^4: modern ways of doing web services

the consistent POST over HTTPS wins because the URL includes the noun AND the verb. REST cares too much about your abstractions and object representation

hilarious

Comment on Re^4: modern ways of doing web services - avoid REST too

Replies are listed 'Best First'.
Re^5: modern ways of doing web services - avoid REST too by Rhandom (Curate) on Sep 28, 2013 at 20:10 UTC
If you are revealing your abstractions (like REST requires), always POSTing of HTTPS wins because the noun and verb are kept together. However, always POSTing over HTTPS does not require that you always have a noun and a verb. So if you are playing by RESTs rules, always POSTing over HTTPS wins. But always POSTing over HTTPS wins because you don't have to reveal your abstractions. You seem to be an easily amused guy who picks the contexts he likes while ignoring the larger picture. my @a=qw(random brilliant braindead); print $a[rand(@a)];	[reply]
Re^6: modern ways of doing web services - avoid REST too by Anonymous Monk on Sep 28, 2013 at 21:58 UTC
You seem to be an easily amused guy who picks the contexts he likes while ignoring the larger picture. You seem to have a miserable impression of REST , REST is not bondage -- GET/POST -- yeah, thats what html forms support, that is REST -- even if you go full vocabulary because its easy if you're using jQuery for JSON/POSTing/over-HTTPs, it is consistent , you should be GETing/POSTing 90% of the time REST is easy going and as consistent as you want it to be	[reply]