magnet link handling bugs
 

hello.

imagine this situation

my friend sends me this magnet link:



ischgl_snowboard_360_2007_anuell.mov
magnet:?dn=ischgl_snowboard_360_2007_anuell.mov&xt =urn:sha1:<sha1-hash>&xl=174122

it contains filename, size & hash....

good. phex catches the download and tries to find this file in the gnutella network....

okay, but then discover that the same file hosted via http too here:

http://pipecheckphp.sourceforge.net/http2p2p/v1/demo/

i go to the site and click the new magnet-link to this file there

ischgl_snowboard_360_2007_anuell.mov
magnet:?dn=ischgl_snowboard_360_2007_anuell.mov&xs =http://pipecheckphp.sourceforge.net/http2p2p/v1/demo/index.php/.././files///ischgl_snowboard_360_2007_anuell.mov&xt=urn:sha1:< sha1-hash>&xl=174122
.

this is the same magnet-link but it includes a http-source of the file.

now when i click this link PHEX says "you already download this file" and phex then refuses to take new parameter into the download, so that PHEX tries to get the file from the newly gathered HTTP-source.

can you reimplement your magnet handling so, that existing download get updated with the new magnet data in case a new link is entered, please?

Thanks for your time and the :super: PHEX :)

(EDIT: Removed the sha-values of the magnets (forum-policy: no magnets, since we can't check their content easily (and need to be careful, so the rule gets enacted universally). But since the magnets are necessary for the example I only masked the sha1-values. For those interested, the magnet is avaible [url="http://pipecheckphp.sourceforge.net/http2p2p/v1/demo/index.php">at sourceforge[/url] - Arne).

I like the idea!

I don't know how much work the redesign would be, but merging sources sounds great!

Phex already merges new search results into the downloads, so maybe the merging of new magnets could be done using the same routines...