On Tue, Apr 17, 2001 at 12:51:06AM +1200, David McNab wrote: > I've got a dilemna with client design: > > I've seen lots of cases where newer inserted keys can't be found by others > unless they use ridiculously high HTLs. > > Which brings me to a question: > In order for a client to be useful, there needs to be a high (90%+) success > rate with retrieving previously inserted keys. > > I can see two ways to go: > 1) "Push hard" - the client inserts keys with high HTLs, and takes forever, > but the keys can be retrieved by others quickly and with low HTLs. > or > 2) "Suck hard" - the client inserts keys with modest HTLs, but requests keys > with very high HTLs - insertion would be quick, but retrieval would take ages. > > Anyone got any thoughts on which strategy is best in the bigger view of > things?
Push hard uses up a heck of a lot of space on the network to make it easier for the users to get the file. If the file isn't popular you've just wasted a big pile of space. OTOH it's nice on users and there is a low chance of the file dieing out before anyone can request it, which if that happens is a big waste of space. Suck hard OTOH has a relatively high chance of losing the file completely due to the low number of inital copies. If the file is popular it'll take awhile for the file to be distributed around the network. For the individual who wants his or her file to be seen push hard is probably the way to go. All the freesites are using HTL's of at least 50, 100 in the case of snarfoo. -- GCS d s+:-- a--- C++++ UL++++ P L+++ E W++ N- o K- w-- O- M V- PS+ PE+ Y+ PGP+++ t 5 X R+ tv-- b+ DI+ D++ G e- h! r-- y-- pete at petertodd.ca http://retep.tripod.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010416/8cb1a6fc/attachment.pgp>
