Comments on: Restlet available on Android phones

By: Restlet, a RESTful middleware for GWT, GAE and Android « Noelios Technologies

Thu, 17 Dec 2009 19:47:09 +0000

[...] Android for deployment on compatible smartphones [...]

By: Jerome Louvel

Jerome Louvel — Wed, 26 Aug 2009 17:14:18 +0000

Hi Harold,

It not unRESTful at all. You might want to use query parameter to control the depth of your representations. Having both seem useful.

What also seems important is to be able to access to each friend independently, if necessary.

Best regards,
Jerome

By: harold

harold — Wed, 26 Aug 2009 08:16:38 +0000

Hi,
i have a question about using Restful-Webservice with Android. For example i have a Webservice where i save all my contacts/friends. So in Rest every Friend is a Ressource. For example if i have 20 Friends, then the Client asks for the Friends and gets a List of 20 IDs, and then he must make 20 Request to get Information of every Friend. If im making a URI like “…/clientid/getallfriends” on the Serverside, from which i get directly all 20 friends in the Response, then its a anti-pattern in REST. But how can the first solution be efficient in the mobile evironment, cause the network is slow and unreliable and every request needs batterypower? In the first solution i have 1+20 Requests, in the second i have only 1 Request. I really want to understand. Thank you

By: Restlet 2.0 M4 released « Noelios Technologies

Restlet 2.0 M4 released « Noelios Technologies — Tue, 25 Aug 2009 10:05:16 +0000

[...] that we support: Java SE, Java EE (with Servlet support), Google Web Toolkit, Google App Engine and Android. In addition, the porting of the main source code base to each edition is now fully automated, [...]

By: selem

selem — Mon, 10 Aug 2009 12:50:01 +0000

url to the android sample application should be http://wiki.restlet.org/docs_2.0/13-restlet/275-restlet/266-restlet/269-restlet.html. the blog post refers to a 404 location.

By: Restlet 2.0 M3 released « Noelios Technologies

Restlet 2.0 M3 released « Noelios Technologies — Wed, 27 May 2009 09:44:07 +0000

[...] growing number of special Restlet editions (Java SE/EE, Google Web Toolkit, Google App Engine and Android), it seemed appropriate to rename the Restlet 1.2 branch into Restlet [...]

By: Jerome Louvel

Jerome Louvel — Thu, 07 May 2009 07:27:59 +0000

Hi Gabriel,

Yes, we are on the same page. The idea is to fully leverage REST/HTTP to decouple clients and servers which can end-up being located in various places. A key feature is content negotiation which can be leveraged to adjust representations to the capabilities of the clients (GWT, jQuery, Silverlight, Flex, etc.) on the server-side.

Regarding the serialization of values/objects into representations (and vice versa), we are making significant progress for our next Restlet 2.0 release (due at the end of 2009). See for example the new ConverterService and the new Resource API.

Best regards,
Jerome

By: Gabriel Kastenbaum

Gabriel Kastenbaum — Wed, 06 May 2009 22:09:53 +0000

I do agree with your way to see the future:
* services availables “somewhere” – on a Google App Engine plateform or any other plateform.
* Different types of clients : Android, but also RIA clients – flex, but why not javascript clients written with GWT or with JQuery?
* Communication with REST services. Here we need Restlest. Or – why not – if you are on a php server – using some php script
With that kind of architecture developping available services become easy. Then you just have to convert and integrate the values that you receive – this is not the smallest part in reality, but this part should be improved in the future. If you are interested, you can have an eye on our blog where we published some studies about that kind of architectures and where we related the problems that you can encounter – it’s in french (blog.oxiane.com)