Hi Adam,
Regarding Restlet Framework, its implies a resource-oriented design
(resources, URIs, representations) and proper usage of HTTP
application-level features (conneg, caching, conditional requests, etc.).
However it doesn't force interaction between clients and servers to go
through hypermedia even though we help with that via template engines, HTML
form parsing and so on.
We do already have support for machine-to-machine interactions in the form
of annotated Restlet interfaces which do involve a coordinated deployment
of clients and servers.
So concretely there won't be any fundamental change moving forward but
probably more support for machine-to-machine interactions around the Web
API style, which people have been looking for anyway for a long time (e.g.
how to document / version my API).
Best regards,
Jerome
--
http://restlet.org
http://twitter.com/#!/jlouvel
2013/5/3 Adam Mc a...@cs.miami.edu
Jerome, this was a good post and lots to think about. I don't have any
feed back right now, as much of the conversation was new material for me,
but I tended to agree with what Hansson posted.
Are you planing on moving Restlet towards more of the Web API style
framework, as opposed to a streamlined REST framework? I got that
impression from your blog post that is what you might be thinking.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3054829
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3054840
