HCVService

2013-01-16: init, damn it...

2013-01-21: meet difficulty to use writerequested() correctly. Those examples on the net are used to send messages immediately; through our app requires one channel to wait for all messsages collected from the other clients, compute them together and thus send them back. Still working on it...

2013-01-23: Today I still didn't find a way to write back the message gracefully without knowing how to pass write-backed message to workers controlled by netty itself. Damn it...

2013-01-24: SEVERE CHANGE! Decide to manage every message either by channels or monitor including sequential number as well as timestamp. Allow clients will send floods of messages and server replies according to its current result. (Take a look on enum WRITETYPE for details) Here I assume network delay is less important than computational delay*, and will be corrected right after the testing.

2013-02-06: Replace usage of Calendar() with System.currentTimeMillis()

2013-02-20: Add a new protocol state called MSYNC to synchronize data of virtual object named voMain and present its rendering. (NOTE) Here comes a framerate issue that engine(server-side) used to deliver voMain's latest position with framerate M and window(client-side) draws it according to received data with framerate N. However, voMain's speed seems to be limited for some reasons. Need to be verified.