Yes. The number of threads that handle the eventQueue in SessionBuffer per session is at most 1 at the same time. That's how the message order is maintained.
HTH, Trustin On 10/26/07, tiandike <[EMAIL PROTECTED]> wrote: > > then the number of thread that handle eventQueue in SessionBuffer for one > connector(session?) is at most 1 at the same time? > > > Trustin Lee wrote: > > > > On 10/25/07, tiandike <[EMAIL PROTECTED]> wrote: > >> > >> I debug the source code and find it's SessionBuffer to maintain the > >> order , > > > > True. > > > >> and i find one connection with one thread for handler (Thread > >> [pool-4-thread-4] ). Is this right? > > > > No. Thread is allocated on a per-event basis. If it's allocated per > > session, we will have to create too many threads and won't scale. > > > > HTH, > > Trustin > > -- > > what we call human nature is actually human habit > > -- > > http://gleamynode.net/ > > -- > > PGP Key ID: 0x0255ECA6 > > > > > > -- > View this message in context: > http://www.nabble.com/why-client-received-message-in-order--tf4668688s16868.html#a13423898 > Sent from the Apache MINA Support Forum mailing list archive at Nabble.com. > > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
