Christian Biere wrote: > >Lloyd Bryant wrote: > > Updated to r14887, and the switch from the main download to the THEX > > download works beautifully. On three tests, using Bearshare "push" >sources, > > it switched, and received the THEX data without a hitch. > > > Now for the bad news - it's doesn't switch back once the THEX download >is > > done. I can manually restart that download after the THEX has >completed, or > > I can wait out the timeout and the download will restart on it's own. >For > > common files, with many sources, this is not really a problem, but would >be > > a bit of a nuisance for rarer files (especially when dealing with "push" > > sources, where there's a chance that the push route will be lost during >that > > timeout). > >I haven't tested it excessively yet but if you update from SVN, this should >now work as well. gtk-gnutella tries to continue requesting even after it >fully completed a file (or other kind of download like THEX). >
Updated and ran some tests. I appears to be switching back an forth between normal and THEX downloads without any problems. Cool :-) > > Something more troubling - I've seen two THEX downloads since updating >where > > the THEX status is "Max number of downloads...", but when I check the >main > > download, the same source shows a status of "HTTP 503 Full at...". > >I'm not sure there's really something wrong with that. Maybe the peer >didn't >send any Retry-After header, BearShare and Shareaza do that which might >cause some extra request delay. > > > I've also caught it once creating the THEX download from a "Queued..." > > source, which I had never seen before (I was under the impression that >it > > only used "active" sources when deciding where to download the THEX data > > from). > >"Queued" is kind of active. Poor wording strikes again. What's displayed >under "Active" are files which are currently receiving data from sources. >Under "Queued" you see only "remotely queued" files i.e., it does not >refer to files in the local queue. The files shown under "Queued" may also >have a connection, if they are "actively" queued. As these connections >are polled periodically, you might see them switching between different >requests as well. Both of these are probably non-issues, then. I was thinking that attaching the THEX download to a "HTTP 503 ..." or "Queued..." source might result in the main download completing without any THEX data being received, but testing with some large .avi files, I have yet to get the download completed without receiving the THEX data. I haven't tested yet with smaller files, but logically if the download is short enough, then we don't really need the THEX data anyway. Lloyd B. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
