hello dude,
this is not the best sort of email one can hope getting any help for. if
it's really an advertisement for a new project, then congratulations but
pls. next time re-word the subject line accordingly.
if on the other hand, this is a real cry for help and an earnest desire to
contribute for improving the code then consider the following aspects which
you may have overlooked --if you haven't you didn't make it clear enough in
your email:
* GET and POST parameters: Restlet abstract the HTTP request in a Request
object --a subclass of Message-- both live in the org.restlet.data package.
if you look at the source (or the javadocs) you'll see a wealth of methods
that should be able to suit many and varying needs; e.g.: getEntity() which
returns a Representation, and getEntityAsXxx() methods. having obtained,
for example a Form instance (from getEntityAsForm()) you can then have in
your concrete Resource type something that would materialize a Data Access
Object (DAO) for the object type represented by this Resource in a way
similar to the following:
public class MyObjectResource extends Resource {
public MyObjectDAO getDAO(Form f) {
final MyObjectDAO result = new MyObjectDAO();
result.setNickname(form.getFirstValue(nickname));
result.setFirstName(form.getFirstValue(firstName));
...
return result;
}
}
* Asynchronous communication: Restlet does not impose any communication
model or technology. how the call arrives to a Restlet Connector is in a
way orthogonal to how it is dealt with. if you're like me convinced of the
value of REST and its stateless nature, then leaving this out of the
concerns of the library / framework could only be beneficial. my opinion is
that if your application really needs something like that build a layer that
sits outside and in front of any REST-ful tier.
* Should have option to run as webapp: Restlet already allows you to do
that. in addition it allows you to run your Server application outside any
J2EE WebApp Containers --see the Grizzly and Simple Extensions.
* Use Jetty for standalone: i presume you meant for Server standalone,
since with Restlet you can build Clients as well as Servers that communicate
in a REST-ful manner. i personally don't like being herded to use one type
of software however good it is --and Jetty is definitely a first grade piece
of software. but if you think that this could facilitate the adoption of
Restlet and REST in general, nothing prevents you from exploring the Servlet
and Jetty Extensions and identifying any weaknesses and submitting
improvements.
* Too Complex: this is like Beauty; it's in the eye of the beholder! i
would love to see pseudo code that gives concrete examples of how it could
be made easy --something like Before and After. seriously, there may be
areas where you need to wire lots of parameters and objects but the fact
that at the base line it's flexible to allow you almost complete control on
how to handle a request-response chain, for me this is an advantage. that
said, if you think there are representative Use Cases which would benefit
from cut down versions or reduced functionality of some classes and
operations, then may be you can propose either new classes to offer this
functionality or ultimately a new Extension (RestletMadeEasy?) that would
benefit developers with such needs. if the API exposed by these classes is
appealing i'm sure developers would move to adopt it. of course you can go
and write such a beast from scratch, or you can build it on top of Restlet.
your choice.
On Sat February 7 2009 05:24:39 code dude wrote:
Hi folks ,
I used restlet on one my projects which live since one year , i fond
RESTLET to be too complex and confusing also it lacks some features like
(i maynot be aware if features might exist)
- restlet get or post parameters should be automatically mapped to
some kind of object
- asycn communtication should be supported
- restlet should have option to run as webapp on tomcat or jetty
- Pl use jetty for standalone
- its too complex !! too many new concepts , use KISS
so i am writting my own trimmed down RESTLET framework using jetty
continuations , I hope opensource when its done
Best Regards,
Code Dude
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=11
14069
cheers;
rsn
signature.asc
Description: This is a digitally signed message part.
