Jérôme,
Could you elaborate on your most recent comments in the Support
asynchronous processing issue?
http://restlet.tigris.org/issues/show_bug.cgi?id=143
In particular, what would the Response autoSent property mean?
--tim
: Restlets and Asynchronous Request Processing
It's probably best in that case for handle to return a
Future-like object that lets you wait for completion or
cancel. Then Restlets that implement asynchronous handle
could use a common default implementation of synchronous
handle like
to share
your ideas openly. I don't know if mine would be any better in this domain
:)
Best regards,
Jerome
-Message d'origine-
De : Rob Heittman [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 24 janvier 2008 01:04
À : discuss@restlet.tigris.org
Objet : Re: Restlets and Asynchronous Request
On Jan 23, 2008 7:04 PM, Rob Heittman [EMAIL PROTECTED] wrote:
Getting full value out of asynchronous calls will clearly involve a lot of
careful work across the RI and extensions. It would be a great opportunity
to apply correct and modern Java concurrency patterns -- I hope Tim Peierls
is
Hi all, anything happening with this idea? I'd love to see this move
forward, even if I do have to wait for 1.2. Maybe it could work in 1.1
as an extension?
Thanks!
Avi
On 12/11/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi John,
Thanks for the excellent proposition!
I've been thinking
Hi John,
Thanks for the excellent proposition!
I've been thinking about similar API changes in the past, see this issue:
http://restlet.tigris.org/issues/show_bug.cgi?id=143
Could you add a synthesis of your proposition to the issue tracker as well
as your suggested changes(patches)?
We just
6 matches
Mail list logo
