Sponsorised links
This month
August 2008
ongoing · REST Questions
about the use of PUT and DELETE in the protocol, simply because those functions aren’t supported in browsers, hence also not in servers, and are not available at all to programmers on the dumber class of mobile devices.
Bill de hÓra: REST as an engineering discipline
J'aime ces discussions, car imanquablement, tout le monde peut avoir raison :)No, the issue isn't relative simplicity; it's how complexity is organised.
Qi4j: REST EntityStore and SPARQL EntityFinder = rich client web apps!
Tant de choses à tester...For the finder part I have implemented a SPARQL backend, which internally delegates to Sesame2, which is the same default index/query that is used to find Entities in general. This in itself is pretty cool, because it means that you can write your domain model in Java, have it be automatically persisted in a store like Neo4j, and then with no extra effort expose it through SPARQL for AJAX webapps to consume (both RDF/XML and JSON output is supported today). Minimally writing a domain model only involves writing Java interfaces (no classes), so it's pretty easy to get started.
Sponsorised links
July 2008
OSCON day 1: Beyond REST? Building Data Services with XMPP PubSub - O'Reilly Conferences
Après le WS-*, est-ce que l'on va avoir le XMPP-* :)To solve this problem its key to leave standard REST web services behind and find a way to use message passing, which is a direct communication way of notifying users of changed content.
Convenience Over Correctness :: Steve Vinoski’s Blog
Apache / Sling : développer en Java pour le Web - Journal du Net > Développeurs
June 2008
Wrestling with REST
Il n'y a pas moins de protocole, il y a juste le protocole.REST is cool because there's less protocol there
