RE: Tracker scrape extension proposal

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The client that scrapes and wants five is more common than you think.
Azureus' scrape code allows it to scan the torrents (both active and
not) in the list and scrape all the common-tracker torrents in one
request (when the tracker supports it). It's not uncommon to have a
tracker with 4000 torrents listed and have one client request scrapes
for batches of 5-10 at a time.

How is requesting the scrape information for several dozen (of
several thousand) torrents and getting the scrape information for
several thousand more efficient? It sounds quite wasteful if you ask
me, especially considering the wide support for connection
keep-alives in both clients and trackers.

Because of limitations in the HTTP protocols, there's a limit to the
number of torrents you can request the scrape information for before
the protocol breaks the request, and average users won't reach that
limit very often.

As for your "wasted request" theory, the clients that support
gathering multiple scrapes in one connection KNOW when they request
mulitple scrapes, and KNOW that in the case of them only getting one
back that the tracker doesn't support multiscrape. After finding out
one way or another if multiscrape is supported, they either wait for
the next cycle (in the case of it being supporteD) or request the
remaining scrapes in separate, individual requests.

Two mechanisms is just more code to break trackers AND clients right
now. I've started work on adding support for the current multiscrape
handling in the trackers I help program.

- -----Original Message-----
From: Nick Johnson [mailto:[email protected]] 
Sent: Wednesday, January 12, 2005 11:23 PM
To: [email protected]
Subject: Re: [BitTorrent] Tracker scrape extension proposal


Harold Feit - Depthstrike.com Administrator wrote:

> 
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Taking a look at the way get values are generated in cases of
>multiple paramaters of the same key typically overwrites the value
>in default configurations, preventing other values from being
>available. Other configurations only read the first value, not
>allowing access
>to those after it.
>
>Clients that don't support asking for multiple scrapes in the same
>request will only request 1 at a time, consistent with the way they
>have done in the past.
>
>For tracker-side development, I feel your suggestion of returning
>all torrents when processing multiple info_hash values isn't
>supported is quite damaging to the tracker (pointing back to your
>"thousands of
>torrents" tracker example). If you requested the scrape data for 5
>torrents and got 5000, you would be doing more damage to the tracker
>than getting 5 separate requests.
>  
>
Then perhaps two mechanisms is better. At the moment, I'm requesting
the 
full scrape for each tracker, because individual requests are usually
inefficient. If I could specify a list of desired keys and have it
give 
me them or everything, this would be an improvement in efficiency.
The 
one that only wants 5 (but really, how often will that happen in 
reality?) can use the current mechanism.
As it stands, if I try and use the current system to request more
than 
one hash, I'm quite likely to get a response with only one, wasting a
request.

- -Nick Johnson

- -- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 1/10/2005
 

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQEVAwUBQeYEKV8nceBm0DUaAQLpTQf+NZP339Mxj4jElu/U+wMbEe+4Iy4XQLVK
QNz6x33KCGWdcdHtd5f21GyqpYvKH37Zx3jfI69HH7IbdIPUtjih8ktMoWZJKlzZ
wqPQCTeHoeo0Rr+Id+VP3iwYJtpmc6NS4JP+qf8s/r+gZ9Fy8Dxf+7Mekq+LuSVW
Pbzd7xNX1lSpfLIJsqjXzoLFPEIsqIpKjrX7XHfvyBK9AYqcZfczVgVwNAPFkqEB
yZH6ZK2GtWc91pXcvORkTc9+/POLMg7f1ZkuBfPVs7IM8KNOsGCRxb9boza/eDBH
7vH+e8TuN9qVbedljXf9xV2+SVJSrXvdmk2o9nRCurev7Fb0MJirhA==
=O5hE
-----END PGP SIGNATURE-----




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/BitTorrent/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/