org/documentation/1.0/benchmark
Best regards,
Jerome
-Message d'origine-
De : Rob Heittman [mailto:[EMAIL PROTECTED]
Envoyé : lundi 3 mars 2008 22:45
À : discuss@restlet.tigris.org
Objet : Re: Understanding Restlet's Threading Model?
The mapping of incoming network connections to t
Hi Rob,
Thank you for your reply. I believe the connector I'm using is the Simple one,
since I've put com.noelios.restlet.ext.simple as a dependency in my Maven
project and I don't believe I'm including any other connectors on the class
path. Is there a good way to do a sanity check on this? Al
On Tue, Mar 4, 2008 at 1:52 AM, Jerome Louvel <[EMAIL PROTECTED]> wrote:
[...]
> Now, be aware that web browser generally serialize the request to a single
> target server/domain at least limit the number of concurrent requests sent.
Indeed. From http://www.w3.org/Protocols/rfc2616/rfc2616-sec8
/documentation/1.0/benchmark
Best regards,
Jerome
> -Message d'origine-
> De : Rob Heittman [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 3 mars 2008 22:45
> À : discuss@restlet.tigris.org
> Objet : Re: Understanding Restlet's Threading Model?
>
>
> The mapping
The mapping of incoming network connections to threads is very dependent on
the HTTP/HTTPS connector/server in use. Restlet, as far as I know, does not
do anything to attenuate the native behavior of the server with regard to
creating threads for incoming network connections. Which server environ
5 matches
Mail list logo