Re: Re: Partial file shating!!
rakesh <[email protected]>
| Newsgroups | gmane.network.gnutella.devel |
|---|---|
| Message-ID | <[email protected]> |
Thanks Raphael For Gnutella as per "Partial File Sharing Protocol Version (PFSP) 1.0",The client requests the range it wants using the Range header. Range: bytes=0- means the client wants any ranges the server can provide. The server then provides the range it wants to upload using a 206 Partial Content response. The 206 response contains a Content-Range header on the form Content-Range: bytes <start>-<end>/<total_size> Note that <total_size> is the size of the complete file. If the server is unable to provide any part of the requested range, it returns a "503 Requested Range Not Available" (the Reason Phrase is just my recommendation). If the client continues to request the same range, the server may send a 404 to make a PFSP unaware client stop retrying. The X-Available-Ranges header will tell a PFSP enabled client what ranges it can request. The issue is - I want to know all the parts of a file that peer share. For that I request with "Range: bytes=0-", but none of the peer respond with 206 and "X-Available-Ranges: " headers. They respond with 206 only when I specify random range in the "Range:" headers. That requires a range in Range header which is not known at the time of request. How we can know the all the shared parts of files? Regards [email protected] wrote: Quoting rakesh <[email protected]> from ml.gnutella.dev-forum: :According the specs, servers who has partial file should respond with 206 :Partial Content response on request any ranges the server can provide.But i :never observe 206 response.Server respond with 206 code only when i request with :some range say "Range: bytes=1234-4567". : :Any pointers !! http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.7 Raphael --------------------------------- Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. [Non-text portions of this message have been removed]