Thanks
 

Afisk-

I'm doing fine. Thanks for asking. I'm glad to hear Sparky will be used in later phases of the Gnutella evolution. The diagrams were especially helpful in visualizing the concept. When do you expect to see this supernode/client scheme to be realized?

Again, thanks for your reply.
:-)

I had a SuperNode running when I left the office on Friday - let's see if it is stable and still running after the weekend...

@natalie:

I found that the LimeWire installer may need to download additional components of the InstallShield system while preparing the installation - this may depend on the operating system you are running. If it is not able to download the proper components, and therefore is unable to complete the InstallShield system, then it most probably won't be able to complete the installation of LimeWire, too.

REPLT TO LIMEWIRE: attention Adam
 

Hi Adam,

I took your advice and restarted the limewire "supernode" client but still no luck.
The auto connect hosts just dont respond for some reason. It doesnt even appear to try and connect.
Its as if it forgets to. With Limewire 1.8 it autoconnects just fine. I had this same problem with "Sparky".
If I try to change the port via the options menu Limewire will just hang.
Im really eager to test out this beta. Sice I run Limewire 24/7 and am running off a cable modem I might have the resources to be a supernode.

Thanx again,
Mark P

Re: Thanks
 

> When do you expect to see this supernode/client scheme to
> be realized?

It was a long time ago that FreePeers (BearShare) created something called Defender (Before Defender was Reflector, by Clip 2). Defender too used the client/server model, where these "supernodes" handled most of the traffic, allowing low bandwidth users to connect to the supernodes and chat, search, save bandwidth, etc.

But a long time ago, expecting to implement the supernode/client model was a bit unrealistic.

Using Linux I encountered a little bug. When the download of a file is complete, it remains in the download-list although I checked the 'remove completed downloads' option. Moreover, the client tells me it is still downloading the file at 0k/s although the download has reached a 100% and the downloaded file has already been moved to the shared-folder.

Thanks for reporting this Linux errror. We'll have a look at it as soon as possible. If you're a programmer, you could also take a look at the source at www.limewire.org =). We'll fix it though, thanks!

I am not really sure why Vinnie never released Defender -- we have never really spoken with him about it at great length. The LimeWire "superpeers" are a similar concept with some slight changes here and there.

We expect to release our superpeer implementation quite soon -- sometime in the next month or so, if not sooner.

woohoo!
 

SUPER-PEER! SUPER-PEER! SUPER-PEER! She's SUPER PEERY!!


SUPER-PEER!!.....






get it? yeah....shutup.

vinnie
 

We didn't release it for a couple of reasons:

1) Proprietary implementation = bad

2) Inadequate discovery method for servers (relying on broadcast queries)

3) Uploading the entire index of files was expensive for modem users, and required a lot of extra work when the local file indexes changed (QRP solves this better, both technically and legally)

I think the LimeWire supernode implementation solves all of these problems and that's where we are going.