DefaultSessionEventHandler.doEventHandlerMethodLookup should use multiple threads.

[jacarrichan]

Currently a client session using an instance of the handler, and the handler is a single thread. A client has sent in two events here. When the server is processing the first event, the second event will not be processed. I think DefaultSessionEventHandler.doEventHandlerMethodLookup should use multiple threads.

[menacher]

@jacarrichan this is by design an "event loop" that uses a single thread for high efficiency, just like nodejs and even netty event loop. So events within a single session are always done in the order they arrive. This ordered processing of events is the best default for games.

Of course there are cases where long running tasks, say access to database etc need to be handled, for such cases yes it should be multi-threaded, for that you will need to use another implementation(read your own!) of SessionEventHandler, the DefaultSessionHandler will not be useful in that case.

[jacarrichan]

thanks