On 3/14/07, Coding Horse <[EMAIL PROTECTED]> wrote:
Thanks for the quick reply. But Jian's concern still exists, right? "Yes, this should work; but, personally I think there might be some side effect for this solution; since this either implies to create a IoHandler per session or a IoFilter per session to bind the specific attribute value to the specific session. For a long-running server, it would be better if we can create less objects per session. "
Well, this issue is related only when you use an alternative that uses a constructor. It's not related to SessionAttributeInitializingFilter at all.
I have another question. I want the IoHandler to know who(which object) creates a specific connection(session). What is the recommended way to do this?
If I understood your question correctly, it's IoSession.getService(). It returns IoService, so you need to downcast it to IoAcceptor or IoConnector. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
