GWC

From Shareaza Wiki
Revision as of 12:53, 4 July 2009 by Ocexyz (talk | contribs) (→‎Breakdown Of The Gnutella Web Caches:: correction of comments)
Jump to navigation Jump to search
  Languages:

[[::GWC|English]] • [[::GWC/de|Deutsch]] • [[::GWC/es|Español]] • [[::GWC/fr|Français]] • [[::GWC/he|עברית]] • [[::GWC/it|Italiano]] • [[::GWC/nl|Nederlands]] • [[::GWC/pl|Polski]] • [[::GWC/pt|Português]] • [[::GWC/ru|Русский]] • [[::GWC/zh-hant|‪中文(繁體)]]

e

<Start of recovered content from sabotaged pp.net. It need to be verified and updated if needed. If there was any backuped content aviable it will be bellow recovered content for verification purposes. Please do not remove parts about older system versions, they are needed for many users, but add info about newer and mark them as such. This info should be removed after that verification and update, but only when this page in this language version will be actual and ready to use.>

<This iste is not fully recovered yet, under recovery still>

Gnutella Web Cache

Gnutella requires Gnutella Web Caches (GWC) to get IPs to establish a connection to the network. These are critical to ensuring the health of the network. If you have a dedicated server and can spare some extra bandwidth then please consider running a GWC. People that don't have a dedicated server or are on normal broadband consumer lines should not run a cache from home.

A GWC is a simple script that can be put on any webserver that supports one of the following scripting languages:

PHP (Tip: PHP GWCs are usually the easiest to run and setup on a server.)


Breakdown Of The Gnutella Web Caches:

<comment: Bellow is content of tabel, but sb is needed to set it properly. Sorry. There is full content>

Cache:

Gnutella:

Gnutella2:

Spec 1:

Spec 2:

Flat-File:

SQL:

Installer:

Other Networks:

Different network instances: Beacon Cache (Core 2)

Yes

Yes

Yes

Yes

Yes

Yes (As of 0.2.0 Alpha)

Yes

Yes

Yes Beacon Cache (Core 1)

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes Skulls

Yes

Yes

Yes

Yes

Yes

No

No

Yes

Yes JumsWebCache

Yes

Yes

Yes

Yes

Yes

No

No

Yes

Yes GnuWebCache (Perl)

Yes

Yes

Yes

Yes

Yes

No

No

Yes

Yes GnuWebCache (PHP)

Yes

No

Yes

No

Yes

No

No

No

No GhostWhiteCrab(GWC)

Yes

Yes

Yes

Yes

N/A

Yes

No PHPGnuCacheII

Yes

Yes

Yes

Yes

No

Yes

No

No

Yes Bazooka

No

Yes

No

Yes

Yes

No

Yes

No

No Cachechu

No

Yes

No

Yes

Yes

No

No

No

No Perlgcache

Yes

No

Yes

Yes

Yes

No

No

No

No Gerry GWC (v2)

Yes

No

No

Yes

Yes

No

No

No

No Gerry GWC (v1)

Yes

No

Yes

No

Yes

No

No

No

No Lynn

Yes

No

Yes

No

Yes

No

No

No

No LynnX

Yes

No

No

Yes

Yes

No

No

No

No

<End of table content>

Shareaza Specific Details

  • Get String Breakdown:
         o Update a leaf
               + "?update=1&ip=(ip):(port)&x_leaves=(leaf count) 
         o Ping Variable
               + Appends &ping=1 to identify the cache name in debug messages (for gnutella and gnutella2 in 2.4.0.0, but only for gnutella2 now in 2.4.0.X for spec1 cache compatibility).
               + This feature new to Shareaza. 
         o Network Variable
               + Appends &net=gnutella2 on Gnutella2 queries.
               + Does NOT append a network variable on Gnutella(1) queries. 
         o Client Name / Version Format (2.4.0.0 and earlier):
               + &client=(Shareaza 4 letter code (RAZA / RAZB) )
               + &version=(Shareaza's version) 
         o Client Name / Version Format (2.4.0.X):
               + If Gnutella
                     # &client=(Shareaza 4 letter code (RAZA / RAZB) )
                     # &version=(Shareaza's version) 
               + If Gnutella2
                     # &client=(Shareaza 4 letter code (RAZA / RAZB) )+(Shareaza's version) 


  • GWC Response Matching:
         o i|
               + Informational output alone will not be taken as GWC 'success.' 
         o i|access|period|(time in sec.)
               + Time in seconds before Shareaza is allowed to make a request to the cache. 
         o i|update|period|(time in sec.)
               + Time in seconds before Shareaza is allowed to update to the cache. 
         o i|force|remove and i|update|warning|bad url
               + Remove the GWC from the internal list. 
         o Some Response Matches (added in 2.3.1.X)
               + i|NO-URL-NO-HOSTS
                     # Outputs warning of the cache being totally empty to the system log. 
               + i|NO-URL
                     # Outputs warning of the cache having no alternative URLs to the system log. 
               + i|NO-HOSTS
                     # Outputs warning of the cache having no hosts to the system log. 
               + i|warning|
                     # Outputs warning of the cache to the system log. 
               + ERROR Something Failed
                     # Outputs warning of the cache to the system log(Buggy Bazooka GWCs workaround). 
               + i|warning|You came back too early (2.3.1.X)
               + i|warning|client|early (2.3.1.X)
               + WARNING: You came back too early (2.3.1.X)
               + ERROR: Client returned too early (2.3.1.X)
                     # Flood detection for the update side.
                     # Outputs GWebCache(update) Too many connection attempts to the system log. 
               + too early (2.3.1.X)
               + early (2.4.0.X)
                     # Flood detection for the request side.
                     # Outputs GWebCache URL: Too many connection attempts to the system log. 
               + i|update|OK
                     # Outputs "GWebCache(v2) Update Passed: " to the system log. 
               + OK
                     # Outputs "GWebCache(v1) Update Passed: " to the system log. 


  • GWC Response Matching:
         o i|
               + Informational output alone will not be taken as GWC 'success.' 
         o i|access|period|(time in sec.)
               + Time in seconds before Shareaza is allowed to make a request to the cache. 
         o i|update|period|(time in sec.)
               + Time in seconds before Shareaza is allowed to update to the cache. 
         o i|force|remove and i|update|warning|bad url
               + Remove the GWC from the internal list. 
         o Some Response Matches (added in 2.3.1.X)
               + i|NO-URL-NO-HOSTS
                     # Outputs warning of the cache being totally empty to the system log. 
               + i|NO-URL
                     # Outputs warning of the cache having no alternative URLs to the system log. 
               + i|NO-HOSTS
                     # Outputs warning of the cache having no hosts to the system log. 
               + i|warning|
                     # Outputs warning of the cache to the system log. 
               + ERROR Something Failed
                     # Outputs warning of the cache to the system log(Buggy Bazooka GWCs workaround). 
               + i|warning|You came back too early (2.3.1.X)
               + i|warning|client|early (2.3.1.X)
               + WARNING: You came back too early (2.3.1.X)
               + ERROR: Client returned too early (2.3.1.X)
                     # Flood detection for the update side.
                     # Outputs GWebCache(update) Too many connection attempts to the system log. 
               + too early (2.3.1.X)
               + early (2.4.0.X)
                     # Flood detection for the request side.
                     # Outputs GWebCache URL: Too many connection attempts to the system log. 
               + i|update|OK
                     # Outputs "GWebCache(v2) Update Passed: " to the system log. 
               + OK
                     # Outputs "GWebCache(v1) Update Passed: " to the system log. 


Gnutella Web Cache Specifications

<end of partial recovery by OCE>



<end of recovered content>

<content recovered from last aviable backup>

Gnutella Web Cache

Gnutella requires Gnutella Web Caches (GWC) to get IPs to establish a connection to the network. These are critical to ensuring the health of the network. If you have a dedicated server and can spare some extra bandwidth then please consider running a GWC. People that don't have a dedicated server or are on normal broadband consumer lines should not run a cache from home.

A GWC is a simple script that can be put on any webserver that supports one of the following scripting languages:

Further Information: