Suitably ambitious!
I'm sure we all have our little issues that we'd like to see prioritized...
Mine is that I would like to see some instrumentation of the servers. My
specialization is super-scalable systems ("the cloud") and this would
make Restlet very sweet for me:
http://restlet.tigris.org/issues/show_bug.cgi?id=1117
I also feel that the asynchronous API could use some more thought (as
well as extending it to all connectors). The threading model has in
essence been well thought-out and solved, but I found some loopholes in
its actual integration into the rest of the Restlet structure (I've
wrote about it to the list). It's still not clear to me if 2.0 will have
actually usable asynchronous support.
-Tal
On 06/06/2010 06:45 AM, Jerome Louvel wrote:
>
> Hi all,
>
> Restlet Framework 2.0.0 is now in sight; we are working on the
> remaining blocking bugs and plan to release it at the end of the month
> or early in July.
>
> That means that it’s time for us to plan for the next steps, always a
> great time! I have summarized our initial ideas on this wiki page:
> http://wiki.restlet.org/developers/175-restlet.html
>
> We look forward to reading your comments, suggestions and contributions!
>
> Best regards,
> Jerome Louvel
> --
> Restlet ~ Founder and Technical Lead ~ http://www.restlet.org
> <http://www.restlet.org/>
> Noelios Technologies ~ http://www.noelios.com <http://www.noelios.com/>
>
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2617667
