Hi all,
Tim Peierls wrote:
I hate to sound like a broken record, but the Restlet Request and Response classes are not thread-safe, so Restlet cannot yet take *full* advantage of NIO to break out of the thread-per-request paradigm. (There is movement on this front, however, as Rob Heittman pointed out earlier in this thread.)
I would like to mention that I've completed the work to make Request, Response, Representation and all related classes in API, NRE and extensions thread safe.
It was mostly a matter of adding the right modifier, either 'volatile' or 'final' as there is rarely a need for strong synchronization in those classes. Most of the time they are accessed by one thread at a time.
However, I wouldn't mind having expert eyes looking at the result and making sure everything is ready to support advanced handling, IO and threading scenarios!
Best regards, Jerome
