Asynchronous needs have resurfaced in the context of GWT callbacks this week as well ... so I was just reviewing this thread and RFE.
I am hoping Restlet will be able to expose some of the appropriate concepts in the API, in a non-breaking way, in the short term ... enough to arm us to play further with it. I'm going to be experimenting with some asynchronous designs against the 1.1 trunk, and I hope other people do too. I think this is one of those things that grows better by trying hopeful ideas and seeing where they either excel or fall short, then synthesizing. 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 listening -- and if done right, this would really demonstrate "why Restlet." I like your extension idea ... I had the same notion and was trying to figure out how to actually do it, since most of the good ideas involve modulating core API functionality. I have some ideas, but to spare Jerome the trouble of laughing at them, maybe I'd just better ask ... is this possible, and if so how? - R On 1/23/08, Avi Flax <[EMAIL PROTECTED]> wrote: > > 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 >
