public marks

PUBLIC MARKS with tags rest & "web services"



Jersey : RESTful Web services made easy in Java

by Elryk & 1 other
Implémentation de référence pour construire des web services en RESTful, possibilité d’étendre Jersey avec SPI, livraison du projet avec Glassfish.


Joe Gregorio | BitWorking | In which we narrowly save Dare from inventing his own publishing protocol

by mbertier & 1 other
Ah, so if these issues just turn out to be misunderstandings on your part then Microsoft will just use the APP and not roll out its own protocol? I'm so glad to hear that.

WADL waffling

by mbertier (via)
Joe Gregorio answered some questions about WADL in his post "Do we need WADL?". Also note that Leonard Richardson has chimed in recently on the WADL issue. And I of course have some different thoughts. :-)

O'Reilly Media -- Bookstore: RESTful Web Services

by benoit

You've built web sites that can be used by humans. But can you also build web sites that are usable by machines? That's where the future lies, and that's what this book shows you how to do. Today's web service technologies have lost sight of the simplicity that made the Web successful. This book explains how to put the "Web" back into web services with REST, the architectural style that drives the Web.

Automatic Multi Language Program Library Generation for REST APIs

by mbertier (via)
Besides all these negative points, there are very strong positive points as well. OK, SOAP/WSDL might not be the best choice for every application, but for many at least it is a not so bad one. And even if code generation does not always work perfectly, it usually saves a lot of work. There is just this feeling that there should be something simpler, more straight-forward, and more intuitive. And then REST enters the stage. It is not that REST by definition is easier than SOAP/WSDL. In fact, for machines it is not easier at all.

InfoQ: WADL REST API description language getting some attention

by mbertier & 2 others, 3 comments (via)
Last week, Google's Thomas Steiner unveiled that he is working on a Google project for generating language specific client libraries from WADL and generating WADL from documentation examples, tentatively called Google REST Compile and Google REST Describe. Thomas chose WADL as the description language to be used with the new tool, after examining all the alternatives

Joe Gregorio | BitWorking | REST and WS-*

by mbertier & 2 others (via)
If there are many clients then the demands for caching semantics will be begin to dominate. In that case you need to abandon HTTP as just a simple transport and start using the application level semantics of HTTP to start leveraging the caching architecture already built into the Internet.

rest-discuss : Message: Sun proposes to apply Web service standardization principles to REST

by mbertier (via)
This is like asking Karl Rove and Dick Cheney to write the Democratic Party platform.

The hidden battle between web services: REST versus SOAP

by mbertier & 2 others (via)
Simplicity is a virtue. And in software development, it's an essential virtue. The venerable Jargon File has long had a particularly good adjective for systems that aren't simple: They are baroque.

The hidden battle between web services: REST versus SOAP

by nhoizey & 2 others (via)
Almost everyone has at least heard of SOAP. Few people have heard of REST. But both are jockeying for the mindshare of developers trying solve problems building applications on the web. REST by virtue of existing, and SOAP largely by virtue of backing by software vendors and standards bodies.

Radovan Janecek: Nothing Impersonal: Mental Exercise

by nhoizey
Is HTTP GET/POST enough for you? Fine. Then you are simply not the 'right target' for web services evangelists ;-)

Radovan Janecek: Nothing Impersonal: September 2004 Archives

by nhoizey (via)
Will there be still 97% of simple REST services on the web then? Yes, sure. WS-* does not compete with browser-oriented applications or simple-get-then-do-regexp interactions

REST Eye for the SOA Guy (Middleware Matters)

by nhoizey (via)
my latest Internet Computing (IC) Toward Integration column tries to take a middle ground in the ongoing "REST vs. SOA" debate. It's called "REST Eye for the SOA Guy" (PDF) and it attempts to explain, from the perspective of someone like me with a lengthy SOA background, the benefits that REST brings to the distributed systems picture

Sam Ruby: Tolerance

by nhoizey (via)
acceptable levels of tolerance differ depending on whether or not a given operation is safe or not

by nhoizey (via)
to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!


SOAP ou REST, que choisir?

by holyver
Web Services Convention Juin 2004 Comparer ce qui est comparable

Web Oriented Architecture

by holyver (via)
Un petit debat intéressant sur les problèmes de compatibilité entre les différentes versions de Webservices. Heureusement pour vous, il y a ici un article sur les stratégies a adopter pour s'en sortir !

Introduction aux Web Services

by holyver & 1 other (via)
Lors de cette présentation, nous essaierons d'améliorer notre compréhension des Web Services, ferons un survol des normes les plus importantes de l'industrie (WSDL, SOAP et UDDI) et regarderons rapidement quels sont les alternatives d'implémentations (styles et REST). La vidéo :

Active users

last mark : 09/10/2014 01:37

last mark : 07/12/2008 15:51

last mark : 23/07/2008 20:20

last mark : 10/01/2008 09:45

last mark : 11/06/2007 08:17

last mark : 31/01/2007 13:11

François Hodierne
last mark : 18/11/2006 12:22

last mark : 05/11/2006 06:56