This appears to lend itself to the trend towards dynamic client side applications. The trick ultimately comes down to telling the client what the server is looking for. Turn your applications into...
This appears to lend itself to the trend towards dynamic client side applications. The trick ultimately comes down to telling the client what the server is looking for.
Isn't that essentially what REST has always actually been about? Pretty sure that's what the author of the post is referencing when they say "I won’t tell you where this idea comes from and who is...
telling the client what the server is looking for
Isn't that essentially what REST has always actually been about? Pretty sure that's what the author of the post is referencing when they say "I won’t tell you where this idea comes from and who is that “somebody else.” That's a subject for another post. For now, I can only say it’s time for you and me to get some rest." It's not just the idea of using HTTP as the transport for the API, it's about having a semantic conversation between the server and client where the server tells the client what it wants and where it wants it posted.
Might be. It was an interesting read none the less. Being RESTful might lend itself to conversational APIs, but it is definitely not a necessity. We have all seen one way "conversations" in the...
Might be.
It was an interesting read none the less. Being RESTful might lend itself to conversational APIs, but it is definitely not a necessity. We have all seen one way "conversations" in the RESTful world.
This appears to lend itself to the trend towards dynamic client side applications. The trick ultimately comes down to telling the client what the server is looking for.
Turn your applications into conversations =)
Isn't that essentially what REST has always actually been about? Pretty sure that's what the author of the post is referencing when they say "I won’t tell you where this idea comes from and who is that “somebody else.” That's a subject for another post. For now, I can only say it’s time for you and me to get some rest." It's not just the idea of using HTTP as the transport for the API, it's about having a semantic conversation between the server and client where the server tells the client what it wants and where it wants it posted.
Might be.
It was an interesting read none the less. Being RESTful might lend itself to conversational APIs, but it is definitely not a necessity. We have all seen one way "conversations" in the RESTful world.