Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Parse Releases Their REST API

parse.com

Post reply on HN
Print view View original

1–10 of 36 posts

Re: Parse Releases Their REST API

#5

Post by psadauskas »

KevBurnsJr wrote: post #2

This is an HTTP API, not a REST API. http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

Furthering our wanderings down this off-topic thread, I agree with you completely, but every time I point it out, I get accused of being a "pedant". I've implemented several truly restful APIs, and they've always worked beautifully, but they're internal or private. I tell others about it, and the immense advantages, but they see every other HTTP-RPC API out there and copy that instead.

Why is it that there's no examples of a truly restful web service in practice? The only one I can think of offhand is Sun Cloud's API, which is pretty dead. Its hard to espouse the virtues of a truly restful API when there aren't any examples to point at.

Edit: The downvotes would seem to just further my point...

Re: Parse Releases Their REST API

#6

Post by stanleydrew »

jethroalias97 wrote: post #3
KevBurnsJr wrote: post #2

This is an HTTP API, not a REST API. http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

“When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it means just what I choose it to mean—neither more nor less.”

Are you saying Roy Fielding is like Humpty Dumpty? If so this doesn't appear to be a very useful or enlightening comment.

Re: Parse Releases Their REST API

#7

Post by generalk »

psadauskas wrote: post #5
KevBurnsJr wrote: post #2

This is an HTTP API, not a REST API. http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

Furthering our wanderings down this off-topic thread, I agree with you completely, but every time I point it out, I get accused of being a "pedant". I've implemented several truly restful APIs, and they've always worked beautifully, but they're internal or private. I tell others about it, and the immense advantages, but they see every other HTTP-RPC API out there and copy that instead. Why is it that there's no examp…

If you say you've written some very RESTful APIs internally, perhaps writing an article about the things you've specifically done from most APIs that makes yours RESTful and advantageous vs. a less RESTful API.

Re: Parse Releases Their REST API

#8

Post by [deleted] »

stanleydrew wrote: post #6
jethroalias97 wrote: post #3

Earlier quoted context omitted.

“When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it means just what I choose it to mean—neither more nor less.”

Are you saying Roy Fielding is like Humpty Dumpty? If so this doesn't appear to be a very useful or enlightening comment.

[deleted]

Re: Parse Releases Their REST API

#9

Post by pstuart »

psadauskas wrote: post #5
KevBurnsJr wrote: post #2

This is an HTTP API, not a REST API. http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

Furthering our wanderings down this off-topic thread, I agree with you completely, but every time I point it out, I get accused of being a "pedant". I've implemented several truly restful APIs, and they've always worked beautifully, but they're internal or private. I tell others about it, and the immense advantages, but they see every other HTTP-RPC API out there and copy that instead. Why is it that there's no examp…

I upvoted you.

I would like to learn how to do REST "right", and (for me) it's easier to learn by playing with a working example that deals with "real world" issues as opposed to abstract snippets that only show how APIs get used.

Any further insights/examples/pointers would be greatly appreciated.

Post reply on HN