I can't answer the HttpClient side of this but I can the EJB side:
(Bdon't do it. Its not only against the ejb spec, it has to potential to
(Bleave resources hanging out in the wind (memory/processing leak).
(B
(BBradO
(B
(BOn Feb 2, 2004, at 3:35 PM, $B'.'Z']'V'_(B $B'&'S'd'Z'^'`'S(B wrote:
(B
(B> Hello,
(B>
(B> I am planning to use the HttpClient form EJB and have noticed that
(B> HttpConnection uses threads to implement the connection timeout
(B> mechanism. The way the threads are used shouldn't create any problems
(B> with the EJB programming restrictions about threads.
(B> But I would want to hear your opinion as well.
(B> Also can you explain why the HttpClient is considered faster than the
(B> Sun
(B> implementation.
(B>
(B> Regards,
(B>
(B> Milen
(B>
(B>
(B> ---------------------------------------------------------------------
(B> To unsubscribe, e-mail:
(B> [EMAIL PROTECTED]
(B> For additional commands, e-mail:
(B> [EMAIL PROTECTED]
(B>
(B
(B
(B---------------------------------------------------------------------
(BTo unsubscribe, e-mail: [EMAIL PROTECTED]
(BFor additional commands, e-mail: [EMAIL PROTECTED]