Re: [glob2-devel] Finalized Design Idea for YOG

[Stéphane Magnenat]

Take care about the bandwith of yog routing. glob2 may be bandwidth effective, 
but things like voip are not (and removing them would not be a solution). Let 
imagine we are running a game with 8 players at 2 kBps per player.
We have:
2*8*3600 = 57.6 MB per hour
57.6*24*30 = 40 GB per mounth
Even with Terabyte bandwidth we can only hope to host 25 games before 
consuming all the bandwidth. I don't see who would agree to host this (I 
would not).

I understand that using yog as a router would greatly ease programming, but it 
is a huge feature regression. And having a system that works better for the 
player will make much more player to come which wil break the system. This is 
no long term solution.

Please read this paper that explain how to do things correctly with udp :
http://pdos.csail.mit.edu/papers/p2pnat.pdf

I'm conscious that this tread may be another flame, yet it shows some sounding 
issues Cyrille tried to raise. While the way he raised them and the resulting 
flame might have been unproductive, the issue remain: you can't throw away 
part of the design just because it eases programming. Those part, as complex 
as they can be, are there for reasons.

I agree that the network needs refactoring/rewriting, but I think the overall 
design is correct, things just have to be done cleaner, more layered and with 
much better documentation.

Have a nice day,

Steph

-- 
http://stephane.magnenat.net