Re: PeerInfo and PeerId

Hi Petr,

That seems to me as the best way, too! Then we won’t need to change the Uri::operator== implementation (hope I’m not missing something) and in the PeerInfo ctor we could use “0.0.0.0″ as the default host. So, you can change the Uri implementation in your calitko-petr branch and then I’ll merge this branch and update the PeerInfo class, ok?

Just pushed a revision! Some tests are failing now, you’d be able to fix them faster than me. I’ve written \todos on some places where further changes might be necessary.

Regards,

Peter

Would you like to post a relpy?


This post is a reply to:
Re: PeerInfo and PeerId
Hi Peter, Maybe using the Uri for the internal representation of PeerInfo was not a good idea after all? Or maybe we shouldn’t use PeerInfo in TrackerRequest but instead pass the (more...)

No follow-ups yet.