QuickServer的学习研究（八）
?? 在QuickServer针对通讯的方式的不同可以采用很多形式，但是必须考虑各种交互方式的不同和优缺点：
QuickServer划分其对八类主要开发应用程序逻辑，
????? 服务端和客户端的交互的各种方式如下：
?对于输入的默认DataMode是String，所以如果不改变你将需要设置ClientCommandHandler。
?
?
?
如果服务端和客户端采用java方式那么采用ClientObjectHandler比较好。
采用非相同的语言那么最好采用ClientCommandHandler或者ClientBinaryHandler对象实现两种的交互比较好。
?
?
Mina和QuickServer的优缺点：看来自TrusinLee的评论：
Thank for the information about another network application framework.? I found a few differences:
????????? QuickServer supports blocking mode.? (MINA supports only non-blocking mode, but you can make your operation block at your will.)
????????? QuickServer provides GUI-based admin.? (MINA doesn't have one yet, but will have full JMX support soon, which is a standard.)
????????? QuickServer uses java.util.logging.? (MINA uses SLF4J, which is a safe replacement of commons-logging.)
????????? QuickServer uses its own XML settings.? (MINA provides Spring framework integration instead.)
????????? QuickServer can specify maximum number of clients allowed.? (MINA can do this using a filter, but not implemented by default.? Of course, this will be implemented as an overload prevention filter.)
????????? QuickServer team has one crew.? (MINA has three crews.)
????????? QuickServer project started in 2003.? (MINA started in 2005.)
????????? QuickServer has a difference event handler interface from MINA.? (You'll have to compare it by yourself.? IMHO, MINA has one simple enough handler which covers all QuickServer provides.)
????????? QuickServer doesn't support UDP at all.? (MINA does)
????????? QuickServer doesn't support client-side API at all.? (MINA does)
????????? QuickServer integrated authentication and text protocol in its core.? (MINA didn't and they are considered as a cross-cutting concern that a filter should take care of.? IMHO, MINA is more extensible here.)
?
