From: Kevin Conaway [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2008 2:23 PM
To: discuss@restlet.tigris.org
Subject: Re: StreamClientCall and FH exhaustion
Thanks Jerome.
Matt, could you see if that solves your problem as well? If possible, can you
attach your test case to 439?
On Tu
008 21:18
> > À : discuss@restlet.tigris.org
> > Objet : Re: StreamClientCall and FH exhaustion
> >
> > Yes. If the response is chunked, the stream won't get
> > closed. In general, its not a great idea to close a socket
> > *stream with the intention of clo
]
> Envoyé : mardi 25 mars 2008 21:18
> À : discuss@restlet.tigris.org
> Objet : Re: StreamClientCall and FH exhaustion
>
> Yes. If the response is chunked, the stream won't get
> closed. In general, its not a great idea to close a socket
> *stream with the intention of
e d'origine-
> > De : Kevin Conaway [mailto:[EMAIL PROTECTED]
> > Envoyé : lundi 24 mars 2008 18:47
> > À : discuss@restlet.tigris.org
> > Objet : Re: StreamClientCall and FH exhaustion
> >
> > Assuming the response entity is NOT pre-fetched, what ab
st it isn't happening like this?
Best regards,
Jerome
> -Message d'origine-
> De : Kevin Conaway [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 24 mars 2008 18:47
> À : discuss@restlet.tigris.org
> Objet : Re: StreamClientCall and FH exhaustion
>
> Assuming th
: Kevin Conaway [mailto:[EMAIL PROTECTED]
> >
> > > Envoyé : samedi 22 mars 2008 13:33
> > > À : discuss@restlet.tigris.org
> > > Objet : Re: StreamClientCall and FH exhaustion
> > >
> > > Would it make sense to add an option to
can always issue a
> HEAD request.
>
> Best regards,
> Jerome
>
> > -Message d'origine-
> > De : Kevin Conaway [mailto:[EMAIL PROTECTED]
> > Envoyé : samedi 22 mars 2008 13:33
> > À : discuss@restlet.tigris.org
> > Objet : Re: StreamClie
Envoyé : samedi 22 mars 2008 13:33
> À : discuss@restlet.tigris.org
> Objet : Re: StreamClientCall and FH exhaustion
>
> Would it make sense to add an option to the Client or Request
> that specifies whether Restlet should prefetch the Response
> entity? If the response entity w
away [mailto:[EMAIL PROTECTED]
> > Envoyé : mardi 18 mars 2008 00:36
> > À : discuss@restlet.tigris.org
> > Objet : Re: StreamClientCall and FH exhaustion
> >
> > Its my understanding that the socket can't be automatically
> > closed by Restlet because the respons
estlet.tigris.org
> Objet : Re: StreamClientCall and FH exhaustion
>
> Its my understanding that the socket can't be automatically
> closed by Restlet because the response entity body isn't
> ready until the caller decides to access it.
>
> If this is correct, I
Its my understanding that the socket can't be automatically closed by
Restlet because the response entity body isn't ready until the caller
decides to access it.
If this is correct, I think its up the client to some how alert the Client
or the Response that he is through with the entity
On Mon, M
I have a question around the StreamClientCall code and socket use.
The setup :
We're using a single client (org.restlet.Client) instance through a
number of threads (more than 10 or so), and calling a service repeatedly
that has a 50ms round-trip time. We're using M1 (moving to M2, but more
on th
12 matches
Mail list logo
