> And this includes points 1-4: > No, I won't break the PARQ specs. This is just an idea which I think > could be the successor of the current version. > No, it won't break older clients. Because we can determine by the > queuing version if it can be done, even if we don't it won't break > older gtk-gnutella versions. GTK-Gnutella does not rely on the PARQ ID > but it can make use of it. What I propose could be made transparant and > nobody would notice > > > - After every received request (not only the first), test if the > > requested file exists before queuing. If it doesn't exist, send a 404 > > instead of a 503. > > In which case we break the specs, and you just told me we shouldn't > break previous gtk-gnutella versions.
I should have read this one before my last reply :( If testing if the file exists on each queue re-try, and sending a 404 if appropriate breaks the current specs, then that's a no-no. If Jeroen's idea doesn't break any current specs. and also includes the 404 (or whatever) for a now non-existent file, then it sounds useful to me - reserving a slot for a file, rather than just a slot on the machine seems to me to be the best way of doing things. Sorry there's not much technical insight to this reply, but you did ask for comments :-) Cheers, Jamie ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
