You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Tuure Laurinolli (JIRA)" <ji...@apache.org> on 2007/12/12 03:30:42 UTC
[jira] Created: (DIRMINA-496) AsyncHttpClient creates new
NioSocketConnector
AsyncHttpClient creates new NioSocketConnector
----------------------------------------------
Key: DIRMINA-496
URL: https://issues.apache.org/jira/browse/DIRMINA-496
Project: MINA
Issue Type: Improvement
Components: Protocol - HTTP
Affects Versions: 2.0.0-M1, 2.0.0-M2
Environment: trunk, r598971 of the public repository.
Reporter: Tuure Laurinolli
Currently each AsyncHttpClient creates a new NioSocketConnector. This will cause each AsyncHttpClient to have its own thread pool, which is rather excessive and rather inflexible in my opinion.
Instead of creating its own NioSocketConnector, AsyncHttpClient should receive its IoConnector through a constructor, which should probably be called by a factory. All AsyncHttpClients created using the same factory should share the same IoConnector.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Moved: (ASYNCWEB-8) AsyncHttpClient creates new
NioSocketConnector
Posted by "Mike Heath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ASYNCWEB-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Heath moved DIRMINA-496 to ASYNCWEB-8:
-------------------------------------------
Component/s: (was: Protocol - HTTP)
Client
Affects Version/s: (was: 2.0.0-M2)
(was: 2.0.0-M1)
Key: ASYNCWEB-8 (was: DIRMINA-496)
Project: Asyncweb (was: MINA)
> AsyncHttpClient creates new NioSocketConnector
> ----------------------------------------------
>
> Key: ASYNCWEB-8
> URL: https://issues.apache.org/jira/browse/ASYNCWEB-8
> Project: Asyncweb
> Issue Type: Improvement
> Components: Client
> Environment: trunk, r598971 of the public repository.
> Reporter: Tuure Laurinolli
>
> Currently each AsyncHttpClient creates a new NioSocketConnector. This will cause each AsyncHttpClient to have its own thread pool, which is rather excessive and rather inflexible in my opinion.
> Instead of creating its own NioSocketConnector, AsyncHttpClient should receive its IoConnector through a constructor, which should probably be called by a factory. All AsyncHttpClients created using the same factory should share the same IoConnector.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.