From: Robert Wahlstedt <rob@ma...> - 2009-10-30 15:38:17
Some further info regarding the Netty implementation:
With the Netty rewrite the server now behaves as if using the old
ReducedThreadsSynchronousMode (this setting has been removed from the
config file btw).
This also means that several old config options related to message
queuing are no longer used: MaxUserMsgQueue, MaxGroupMsgQueue,
MaxDatabaseMsgQueue, MaxDispatcherMsgQueue & MaxMsgQueueWait.
There are 3 new settings for how to configure the thread pool that
replaces some of those old settings: ThreadPoolSize,
The MaxLoginMsgQueue is still in use though because I wasn't sure if
logins still needs to be handled extra carefully or not. Maybe the
MUSDBSendQueue should also be kept? It's currently disabled.
The MUSDispatcher class is not really necessary anymore. Messages are
no longer queued there, but rather sent to handleMsg() directly. We
could remove the class and move the methods into MUSMovie instead.
What do you think?
Get latest updates about Open Source Projects, Conferences and News.