[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Re: [GSoC] Restlet integration with Equinox
- From: Rajeev Sampath <rjvranga@xxxxxxxxx>
- Date: Fri, 26 Mar 2010 00:38:09 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=prkgkUpJK9seFjvFGLh+B+l8RU+aNNFy6kmBGgHR9P6dEQ94Ce9cpQJflT3sJWQdbI 8dSqhAWgqAJNw8l1hqM6cKiYVGomPqsqX9e+qeSlQrStjox0ngo1ikCV7fTn4UCB5XOS 0XBPT+l63HOhJuPrQqu8TJRyWFbb+NvSOJyv8=
Hi Jerome, Scott and all,
On Thu, Mar 25, 2010 at 9:12 PM, Jerome Louvel <jerome.louvel@xxxxxxxxxxx>
Hi Scott, Rajeev and all,
Thanks for your interest Rajeev in this GSoC project.
Scott, it seems that the integration of Restlet with ECF could give you with fully-featured server-side REST support. This would also be a nice use case for the GSoC "Restlet integration with Equinox" project.
I've recently created a wiki page for this project. Maybe we could propose another GSoC project for this specific topic?
Otherwise, Restlet 2.0 (currently in RC stage) fully supports asynchronous request processing on both server-side and client-side so it looks like a good fit for your ECF requirements. It also nicely integrates with Jetty 7.0.
Thanks Scott and Jerome, for your responses.
However, now the situation is becoming somewhat complicated to me.
The intent of the original idea is to provide full Restlet integration with Equinox, but what ECF needs seems to be only the server specific part. So there seems to be some redundant work from ECF's point of view (if I haven't misunderstood the situation).
Does it mean that these should be two related but separate projects? (to me, now it sounds like so.)
Also, if the original idea (posted in GSoC idea list) gets selected, which project will it actually belong to?
So I'd really appreciate your ideas to resolve this.
Thanks and Regards,