Trustin, I did see that messageSent was being executed in a thread from the thread pool. I guess my question is: what is the best way to write a multi-threaded client? It seems like things like the protocol encoder (which catches filterWrite, I guess) should run in a pooled thread.
Is it up to me to make sure that happens by executing session.write() in my own external thread pool? If so, what is the use of a thread pool in the IoConnector case, what operations is it speeding up (if not the protocol encoder)? Thanks for your help, Trustin. -Greg On 3/23/06, Trustin Lee <[EMAIL PROTECTED]> wrote: > On 3/23/06, Greg Duffy <[EMAIL PROTECTED]> wrote: > > > > Could someone outline the process for setting up an IoConnector > > (DatagramConnector specifically) to use a Thread Pool? > > > > It seems like no matter what I do, my protocol encoder always executes > > in the IoConnector's thread. I've tried adding a ThreadPoolFilter > > manually in the IoConnectorConfig and in the IoHandler when an > > IoSession is created. I've also tried removing my ThreadPoolFilter and > > using the new default ThreadModel, PooledThreadModel. > > > I ran the NetCat example in a debug mode and it works as I expected; a > thread pool is launched. > > Please try to build MINA from Subversion repository. > > HTH, > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP key fingerprints: > * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E > * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 > >
