I installed LimeWire and checked it's method of receiving magnet
links. It adds itself to the registry, like Shareaza, but LimeWire
doesn't use DDE, just command line. This also means that at current
LimeWire and Shareaza have no communication pipe. Having no
communication pipe means that LimeWire and Shareaza are out of the
scope of xml magnet. They are only considered since the search app
would have to be able to include options from non http bound
applications to really be useful.

I am also concerned about the amount of overhead when using locally
bound http services as a pipe. I think it might be faster to pass
either a magnet link or file path pointing at a MAGMA file along with
a callback command to the handlers. When the handler receives the
magnet link and callback command in it's command line/DDE it would
parse the magnet link to determine what it can do with it and write
the response to a temporary file, then use the callback command to
tell the search app where the response is. The handler could add the
command/DDE information to the registry if/when it supports that.

--- In magnet-uri@yahoogroups.com, Daniel Aleksandersen <pusulv@g...>
wrote:
>
> Yhea,
>
> You should support LimeWire!
> --
> Daniel Aleksandersen
> http://bonaveo.net/
>
>
> On 2006-01-22 , at 05:06, Arne Bab. wrote:
>
> > This is just a litle add on...
> >
> > You should test your draft against LimeWire ( http://
> > www.limewire.com /.org), I think, because that is the major player
> > in the Gnutella Network (Even though I for my part use Phex...).
> >
> > That aside it sounds quite promising, even though I'm not yet into
> > xml-websites.
> >
> > Best Wishes,
> > Arne
>