Project Part 3

In order to use a gnutella network, the user is expected to make a download or come up with an application that is in line with a gnutella protocol. By the use of this application, the user is either made a client or a server. In addition to this, the user acts as a network that is of high level to connect and route data between the client and the server. This network contains several features that makes it user friendly. Just to list a few, it gives anonymity as well as providing ad-hoc networks that have no central control. However, this network demands that several requests be fulfilled to allow for data transmission (Girwodz, Carsten and Surendar 2006).

Gnutella’s response to join requests

In response to a join request, gnutella’s network, through its nodes, generates a network connection from one of the hosts that are familiar within the network (Girwodz, Carsten and Surendar 2006). An always available host immediately after sends the IP address of the client to the peers in the gnutella network. The client is then made a member once the peers accept the request.

Gnutella’s’ response to search requests

In response to a search request, the server accepts the request made by the client through an active connection of nodes. The request received, made in packets, is then sent in inter-nodal intervals until the hops in their predetermined number are attained. Once attained in their maximum numbers, the inquiry for the search is made.

Gnutella’s response to browse request

In response to a browse request, the gnutella network initiates a contact through its nodes from the server with the data required. A port number, IP address then provides a contact that enables the requested data to be browsed.

Gnutella’s response to download request

In response to a download request, the network accepts the request and then negotiates for a file transfer. If the requested file happens to have a firewall, a direct connection is made for the inquiry (Girwodz, Carsten and Surendar 2006). If a firewall is present, the nodes then transmits a request for a push prompting the server to allow the client to make a connection instead for the received inquiry.

Comparing gnutella to napster, while each user sends a download request to be acted upon in gnutella, download are made automatically in napster. This has been made default in napster networking. In napster, users are easily allowed to avoid file sharing as often as they can while in gnutella, discourages users from making direct connection that gives them room for free file sharing.

References

Girwodz, Carsten, and Surendar Chandra. Multimedia computing and networking 2006.

Bellingham, WA: SPIE 2006. Print.