[bittorrent] compact ip problem

Dazen D dazensix at gmail.com
Thu Aug 23 10:23:40 EDT 2007


uTorrent supports both response formats, so there is no bug in it
associated with this issue.  And I'd not call it a workaround as the
tracker sends the spec compliant response when the client
is azureus.

On 8/23/07, Alan McGovern <alan.mcgovern at gmail.com> wrote:
> Obviously azureus doesn't check for duplicate IP:Port pairs (which it should
> be doing).
>
> As for the uTorrent difference, i'd be happy enough calling it a bug in
> utorrent and then a workaround in the tracker (or vice versa maybe). Either
> way, it's not spec compliant.
>
> Alan.
>
>
> On 8/23/07, André <ghost.ued at gmail.com> wrote:
> > well, in my own tests the format in the spec is recognized by Azureus,
> > uTorrent and KTorrent, the 3 clients I've been using to test my
> > tracker responses.
> >
> >
> > The strange detail i've facing about compact responses its that when i
> > send 10 identical peers in a response (10 identical  ip/port pairs )
> > Azureus states he has received 10 peers, while uTorrent states only 1.
> > if i send 9 identical peers and 1 different, Azureus keeps stating he
> > has received 10 peers, while uTorrent starts stating  he has received
> > 2 peers.
> >
> > but in a real world we would not send identical peers, so it doesn't
> matter....
> >
> > Andre
> > _______________________________________________
> > BitTorrent mailing list
> > BitTorrent at lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/bittorrent
> >
>
>
> _______________________________________________
> BitTorrent mailing list
> BitTorrent at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/bittorrent
>
>



More information about the BitTorrent mailing list