REST services are definitely chatty, especially when compared to SOAP
webservices that might perform N operations in one shot.
To me, the chattiness goes hand-in-hand with the HATEOAS concept, where a
client picks its way through multiple server resources via links that are
present in the
I'm not sure if this answers your question directly, but you can definitely
limit accessibility on a resource basis, by using the riap protocol to map
it (see
http://wiki.restlet.org/docs_1.1/13-restlet/48-restlet/86-restlet/45-restlet.htmlfor
a little more detail). Resources mapped using riap
Hi,
You might find the following article helpful:
http://benramsey.com/archives/http-status-201-created-vs-202-accepted/
In general, I think a REST API might handle your situation (a request that
cannot complete immediately) by returning 202 Accepted, along with either
body content or a
I'll qualify this by saying that I know of plans to use APP in enterprise
applications, but I haven't ever actually seen anything in the enterprise.
There's a good presentation on APP's capabilities in non-trivial
environments over at
format
powered by GS1 XML.
-My problem is to understand how makes the client thet have to get or post
a resource to know resource's location and therefore the final url to use in
the GET or POST HTTP messages to refer to the correct locations.
Here your responce
Stephen Groucutt said:
Do
Do you mean, how can a client know what URIs to use when performing service
operations?
It really doesn't have anything to do with Restlet in particular, and I
could be wrong here, but I think this is a still-evolving aspect of REST.
For a while, WADL seemed to be gaining some momentum, but there
Have you tried the version of setEntity that has a MediaType as its second
argument? That should allow you to specify the content type you want to
return. In our project, we use the version of setEntity() that accepts a
String and a MediaType for purposes of returning XML data, and it seems to
I'm not sure if this is the complete answer, but is your tunnel service
enabled, and set to tunnel extensions? You can do something like (from an
Application):
getTunnelService().setEnabled(true);
getTunnelService().setExtensionsTunnel(true);
On Tue, Dec 23, 2008 at 4:04 PM,
Hi Antonio,
You really can use anything that can do an HTTP request - you could use
cURL, you could write something in C++ using boost asio, perl/python have
standard HTTP libraries, and there are many more. I think the only reason
you would need to worry about the Representation classes
I think you can get it here:
http://restlet.tigris.org/source/browse/restlet/trunk/modules/org.restlet.example/src/org/restlet/example/dist/testServlet.zip
Does the FAQ need to be updated, or should that be a valid repository? The
root, http://www.restlet.net, appears to be an unconfigured
I think you must specify the representation type you wish to accept in your
Client.
When you use a web browser to test, the Accept: header field already
contains MIME types that a browser would want to receive, so that would
explain why it works when you view it in a browser. If you have a tool
11 matches
Mail list logo
