From what I understand, ENRON employees were trading MP3 files with gnutella at the time they were asked to shred documents and this is why most documents wern't shred but rather were shared.

Firewalls suck if you want to share files. Reports have it that most push requests take 30 minutes average to come back. What good is that? I think you should do everything you can to educate users on how to set things up to open port 6346.

I don´t know a client which push lives longer than 90 seconds (correct if I am wrong!) - I think the users can´t see the difference between "busy" and "push"!

What I could imagine is that the server is behind a firewall, a push requests is sent but the host is "busy", if the client now automatically retries an other push will be sent etc. until the host has a free slot!

So if you can´t connect within 90 sec, the host is busy!

Morgwen

vinnie speaks and everyone listens

6239 From: freepeers info@f...
Date: Tue Mar 12, 2002 0:07am
Subject: Re: Redundant Push Routes

--- In the_gdf@y..., "Mike Green" <mgreen@e...> wrote:
>
> > It is also interesting to note that the oldest routed push
message
> > was almost 10 hours. This means that 10 hours passed between the
> > receipt of the query hits message and its associated push.
>
> What's the average time, if you know...?

I have that information now. BearShare 2.5.0 Beta 11 includes an
average round trip time between query hits and associated pushes.

I have an uptime of 1h 51m. There were 76 pushes in and 188 pushes
out.

Of the incoming pushes, the oldest round trip time was 38 minutes.
This means that 38 minutes passed between the query hit and an
associated push.

The average round trip time was 21 minutes.

The average is calculated by a running total of push messages and
round trip time seconds (in other words, its accurate).

I would expect that over time, the value oldest would become a lot
more than twice the average.

The real problem: No SOCKS proxy support
 

In my opinion there is just one real problem:

No SOCKS proxy support within the Gnutella clients !

With a SOCKS proxy even a client can open a listening connection (on the proxy itself) and should be reachable, for HTTP proxies the PUSH has to be used, but that does not work between two firewalled clients.

So get the SOCKS proxy support going ! ! !


regards bluepuma

There are some clients with socks proxy support!

http://www.gnutellaforums.com/showth...&threadid=8715

And I think there will be more soon!

Morgwen

any open/public socks servers?

Gtk-gnutella is open source! Or what do you mean?

Morgwen

And Phex!

Morgwen

And LimeWire!

We wouldn't forget that one, would we?

Limewire does not support socks 4 or socks 5 proxies AFAIK!

Read the whole thread!!! :rolleyes:

Morgwen