Sorry for getting back late. I was busy writing some article for a magazine.
2005/11/16, dave irving (JIRA) <[EMAIL PROTECTED]>:
This is a great example that makes us reconsider chain copying. To resolve this we must have only one chain per session, and per-acceptor chain and per-port chain should be added to the per-session chain just before sessionCreated is invoked. It's a little bit overhead, but I think it is fine if we implement it very effectively. Perhaps per-port and per-acceptor chains could be implemented as an array list and used only as a configuration. WDYT?
The solution adds more complex API and will make users confused IMHO.
Trustin
-- As an example:
Suppose during a conversation with a client they request a certain transport encryption mode should be employed. This may result in the handler wanting to configure a filter supporting such encryption at the start of the entire (connection) chain.
The proposed solution would only allow handlers to modify the per session chain - as the other chains are shared by all other connections.
This is a great example that makes us reconsider chain copying. To resolve this we must have only one chain per session, and per-acceptor chain and per-port chain should be added to the per-session chain just before sessionCreated is invoked. It's a little bit overhead, but I think it is fine if we implement it very effectively. Perhaps per-port and per-acceptor chains could be implemented as an array list and used only as a configuration. WDYT?
The solution adds more complex API and will make users confused IMHO.
Trustin
what we call human nature is actually human habit
--
http://gleamynode.net/
