Dear Restlet Community, I've recently become a very happy user of Restlet as both a client and a server. Specifically, I was delighted to see how easy to was to receive a RESTful request and turn around and pass it along to another RESTful service. At first I was thinking I'd need to use something like HTTPClient at that point... then it dawned on me why the "it's a client and a server" approach taken by Restlet is so valuable and it just worked so nice and cleanly!
I'm also very impressed with the quality of the Restlet Community I'm seeing, and I'm wondering if anyone here might have some guidance for me... The question I'd like to humbly submit to the community is: Is there a simple way for Restlet client code to handle multiple simultaneous connections in a highly scalable fashion? What I mean is, when my Restlet code turns around to become a client, I need it to actually make a handful of requests, each to a different server. For scalability purposes, I'd like to be able to do this w/o the overhead of a separate Thread for every request. Is there a "best practice" for this? I gather that there's a lot of discussion and motion in or around this area in the Restlet community. I've heard of libraries like Mina and Grizzly and I'm doing my best to grok them. I'm getting the impression that these libraries try to solve much more than what I'm trying to do, and I'm a little lost in all the complexity. I'm also not clear on what, if any, integration points there are with Restlet that can be put to use right now, or can Restlet do what I need out of the box? Many thanks in advance for any tips or pointers... All the best, Aaron
