On 3/14/09, Dennis Schridde <devuran...@gmx.net> wrote: > Am Samstag, 14. März 2009 16:53:21 schrieb bugs buggy: > > > On 3/14/09, Dennis Schridde <devuran...@gmx.net> wrote: > > > Am Samstag, 14. März 2009 10:28:10 schrieb Kreuvf: > > > > bugs buggy wrote: > > > > > Anyone have any opinions on what should be done? > > > > > > There comes something to my mind: > > > If version checking is implemented in 2.1.3, it should be able to figure > > > out that 2.1.2 (and prior) do not support a versioned network protocol. > > > Thus it should be able to drop connections with people using that... > > > It will be a little bit unexpected for those using 2.1.2, but if we > > > explain this in the release notes, I think it will be less so. > > > > Nope, it can't do that. 2.1.3 sends the 'version_check' message, but > > 2.1.2 has no idea what that messge is, and all we do is return false. > > No error or warning messages at all. :( > > The 2.1.3 client should figure out that it is talking to someone who does not > understand what version_check means, shouldn't it? So the function could > return a failed version check if it does not receive any answer at all. We > could even signal to the user that client X does not support version_check > and > was thus removed from the game. > Please tell me where the flaw is in that thought. > > --DevU > There is no flaw in that thought, after X (5 secs? 10?) if we don't get a echo back, we could kick... just means more coding.
Something like host broadcasts "trunk", and after X, if we don't hear a reply, we kick? I'll try it and see how it goes. _______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
