[ENet-discuss] icmp/tracert/discovering network topology?

[Ruud van Gaal]

Hi,
 
Isn't the ping time more important? In that case, keep ping times on the
server (probably already done by ENet, search the ENetPeer class) and get
the list from the server ordered by ping.
I wouldn't say the distance in computers is of much use for most situations.
 
Cheers,
Ruud


  _____  

Van: enet-discuss-bounces at cubik.org [mailto:enet-discuss-bounces at cubik.org]
Namens Jay Sprenkle
Verzonden: Sunday, January 10, 2010 20:09
Aan: Discussion of the ENet library
Onderwerp: [ENet-discuss] icmp/tracert/discovering network topology?


Good morning,

I'm considering adding some extra features to my enet based peer to peer
application. I'd like the main server to be smart enough to discover which
peers have the shortest connection path to each other. When a peer requests
a list of other peers to connect to then the server can deliver an optimal
list. The only way I could think of to implement this would be to do a
tracert to each peer and sort the list of peers by what common paths they
share. Has anyone done icmp packets with enet? I know it's not it's intended
function but it doesn't seem like it would be difficult to hack together. If
anyone has any better ideas on how to implement this I'd love to hear them.

Thanks!
Have a good weekend




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20100111/cf8b181b/attachment.htm>