How Searches work - Revision history

ArneBab at 15:53, 17 July 2008

2008-07-17T15:53:02Z

←Older revision		Revision as of 15:53, 17 July 2008

	Also, the additional results you see after stopping are those which other clients send in who get your search request.		Also, the additional results you see after stopping are those which other clients send in who get your search request.

-	Stopping the search stops Phex from sending out new requests, but it doesn't stop ~~other~~ from replying to already sent requests, and Phex doesn't throw away results (except clear spam or when requested by the user or a defined and active rule).	+	Stopping the search stops Phex from sending out new requests, but it doesn't stop others from replying to already sent requests, and Phex doesn't throw away results (except clear spam or when requested by the user or a defined and active rule).

-	Spam creates a problem in Gnutella though: The Dynamic Querying protocol stops the searches after about 300 results came in, but its designers didn't take spam into account (at least not the massive amount existing today - back then 3 spam answers on a request were normal, today rare queries often generate hundreds, since companies pay people to spam).	+	Spam creates a problem in current Gnutella though: The Dynamic Querying protocol stops the searches after about 300 results came in, but its designers didn't take spam into account (at least not the massive amount existing today - back then 3 spam answers on a request were normal, today rare queries often generate hundreds, since companies pay people to spam).

	- [http://rakjar.de/gnufu/index.php/GnuFU_en#Network_model:_Change_Searching:_Dynamic_Querying Dynamic Querying explained at Gnutella For Users]		- [http://rakjar.de/gnufu/index.php/GnuFU_en#Network_model:_Change_Searching:_Dynamic_Querying Dynamic Querying explained at Gnutella For Users]

-	Combine that, and rare searches (~~who~~ would only generate 5 or 6 real hits in the whole network) stop after receiving 300 spam results, but no useful result.	+	Combine that, and rare searches (which would only generate 5 or 6 real hits in the whole network) stop after receiving 300 spam results, but no useful result.

	So we need an efficient spam filter to make Gnutella run smoothly again.		So we need an efficient spam filter to make Gnutella run smoothly again.

ArneBab at 15:46, 17 July 2008

2008-07-17T15:46:17Z

←Older revision		Revision as of 15:46, 17 July 2008

	Spam creates a problem in Gnutella though: The Dynamic Querying protocol stops the searches after about 300 results came in, but its designers didn't take spam into account (at least not the massive amount existing today - back then 3 spam answers on a request were normal, today rare queries often generate hundreds, since companies pay people to spam).		Spam creates a problem in Gnutella though: The Dynamic Querying protocol stops the searches after about 300 results came in, but its designers didn't take spam into account (at least not the massive amount existing today - back then 3 spam answers on a request were normal, today rare queries often generate hundreds, since companies pay people to spam).

-	- http://rakjar.de/gnufu/index.php/GnuFU_en#Network_model:_Change_Searching:_Dynamic_Querying	+	- [http://rakjar.de/gnufu/index.php/GnuFU_en#Network_model:_Change_Searching:_Dynamic_Querying Dynamic Querying explained at Gnutella For Users]

	Combine that, and rare searches (who would only generate 5 or 6 real hits in the whole network) stop after receiving 300 spam results, but no useful result.		Combine that, and rare searches (who would only generate 5 or 6 real hits in the whole network) stop after receiving 300 spam results, but no useful result.


	Dynamic Querying is still being used, though, because it provides about 90% bandwidth savings and in theory supports rare searches as well as popular searches.		Dynamic Querying is still being used, though, because it provides about 90% bandwidth savings and in theory supports rare searches as well as popular searches.
		+
		+	- [[User:ArneBab\|Arne]]

ArneBab at 15:45, 17 July 2008

2008-07-17T15:45:19Z

New page

Search requests in Phex run only, as long as they didn't generate enough results (dynamic querying). The % slowly increases nontheless (the cut-off line should be somewhere around 200-300 results.

Also, the additional results you see after stopping are those which other clients send in who get your search request.

Stopping the search stops Phex from sending out new requests, but it doesn't stop other from replying to already sent requests, and Phex doesn't throw away results (except clear spam or when requested by the user or a defined and active rule).

Spam creates a problem in Gnutella though: The Dynamic Querying protocol stops the searches after about 300 results came in, but its designers didn't take spam into account (at least not the massive amount existing today - back then 3 spam answers on a request were normal, today rare queries often generate hundreds, since companies pay people to spam).

- http://rakjar.de/gnufu/index.php/GnuFU_en#Network_model:_Change_Searching:_Dynamic_Querying

Combine that, and rare searches (who would only generate 5 or 6 real hits in the whole network) stop after receiving 300 spam results, but no useful result.

So we need an efficient spam filter to make Gnutella run smoothly again.

Dynamic Querying is still being used, though, because it provides about 90% bandwidth savings and in theory supports rare searches as well as popular searches.