Comments on: Restling with Restlet http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/ adventures in code Sun, 04 Sep 2011 07:24:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Jim Barritt http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/comment-page-1/#comment-8367 Jim Barritt Mon, 02 Mar 2009 16:31:19 +0000 http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/#comment-8367 Thanks David, It's interesting that you found something similar. I will have a look at Mattress. Actually I have been thinking about writing my own framework so will be interested to see what's in Mattress. It also links to <a href='http://jcp.org/en/jsr/detail?id=311' rel="nofollow">JSR 311</a> - JAX-RS: The JavaTM API for RESTful Web Services. Thanks David,

It’s interesting that you found something similar. I will have a look at Mattress. Actually I have been thinking about writing my own framework so will be interested to see what’s in Mattress.

It also links to JSR 311 – JAX-RS: The JavaTM API for RESTful Web Services.

]]> By: David http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/comment-page-1/#comment-8366 David Mon, 02 Mar 2009 16:11:10 +0000 http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/#comment-8366 We re-evaluated our usage of the Mattress Framework (http://mattressframework.org/) recently, to see if we would rather move to Restlet. We concluded that Restlet was way too complex and too feature rich to fit the bill (after being used to the elegant simplicity of Mattress). So we postponed our migration until Spring 3.0 final is out, as we will most likely migrate to their REST support. We re-evaluated our usage of the Mattress Framework (http://mattressframework.org/) recently, to see if we would rather move to Restlet. We concluded that Restlet was way too complex and too feature rich to fit the bill (after being used to the elegant simplicity of Mattress).

So we postponed our migration until Spring 3.0 final is out, as we will most likely migrate to their REST support.

]]> By: Jim Barritt http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/comment-page-1/#comment-8365 Jim Barritt Mon, 02 Mar 2009 16:01:56 +0000 http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/#comment-8365 Hi Lasse, Thanks for the comment. Yeah, In my <a href="http://jimbarritt.com/non-random/2009/02/08/the-future-of-frameworks/" rel="nofollow">previous post</a> about frameworks , I thought I might be really talking about a library. Also Pat picked up on the distinction there too. r.e. Isolating our code from the framework, its a good point, indeed this is what we ended up doing, creating our own API and just using Restlet underneath. One down side to this is that there is more code in the application, so its another level of indirection to go through for anyone maintaining it. Hi Lasse,

Thanks for the comment.

Yeah, In my previous post about frameworks , I thought I might be really talking about a library. Also Pat picked up on the distinction there too.

r.e. Isolating our code from the framework, its a good point, indeed this is what we ended up doing, creating our own API and just using Restlet underneath. One down side to this is that there is more code in the application, so its another level of indirection to go through for anyone maintaining it.

]]> By: Lasse http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/comment-page-1/#comment-8363 Lasse Mon, 02 Mar 2009 15:55:06 +0000 http://jimbarritt.com/non-random/2009/03/02/restling-with-restlet/#comment-8363 > I feel that frameworks should be transparent and non-invasive You mean it should be a library? ;-) Anyway couldn't you get away with delegation at your framework hot spots? Basically, do the simplest possible marshalling and call out to your own classes. Then you could keep your classes pure and only worry about Restlet for integration? > I feel that frameworks should be transparent and non-invasive

You mean it should be a library? ;-)

Anyway couldn’t you get away with delegation at your framework hot spots? Basically, do the simplest possible marshalling and call out to your own classes. Then you could keep your classes pure and only worry about Restlet for integration?

]]>