08-11-2012, 05:29 AM
Are you sure that chunk block serialization: multiple times to multiple protocols will not cause too much overhead? Especially if we're aiming to run on some low-end hardware such as raspberry pi?
And how far that protocol simplification will go? For example touching a repeater results in changing its metadata in specified way, and sending that change. But metadata and other things may change in further versions of protocol. Will it be handled as 'block (metadata) change event' or rather 'repeater changed to 0,3 sec event'? If so, don't you think that 'bridge' class for each protocol will grow to enormous size?
Anyway I'm not that skeptical for your idea. Current packet handling is fast, but with a bit of carelessness causes stability and security issues (see my bug report)... And expanding compatibility without breaking older clients would be a nice unique feature on mc-server.
And how far that protocol simplification will go? For example touching a repeater results in changing its metadata in specified way, and sending that change. But metadata and other things may change in further versions of protocol. Will it be handled as 'block (metadata) change event' or rather 'repeater changed to 0,3 sec event'? If so, don't you think that 'bridge' class for each protocol will grow to enormous size?
Anyway I'm not that skeptical for your idea. Current packet handling is fast, but with a bit of carelessness causes stability and security issues (see my bug report)... And expanding compatibility without breaking older clients would be a nice unique feature on mc-server.