In bish.lists.gtk-gnutella.devel, you wrote: > I think the feature of PARQ, that the clients can change their minds > before reaching a free slot, is indeed a good and necessary feature, so > that the client can choose the _range_ of the file he wants to download > in the last minute. But is this ability, in practice, ever used to > choose another _file_ in the last minute, instead of just another > range? I doubt that. > > IMHO, a "503 Queued" should never be sent when the requested file > doesn't exist (and, of course, a QUEUE callback should also never take > place in that case). And the existence of the requested file should be > verified by the server for every GET request, so that a "503 Queued" is > never sent when the file has been deleted in the meantime. As I said > before, the availability of a requested _range_ should still not be > checked too early, provided that the file exists at all.
I agree that the client should only be able to change it's range, not it's file. I can see no purpose for a servent to change the file it's requesting on the same PARQ ID, unless it's someway of grabbing slots just to hold on to them for later :) (yeah, ok, this is hardly an issue I know, but could happen, I think!) ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
