[p2p-hackers] Tighter HTTP and P2P integration??

[Ian Clarke]

On 14 Feb 2006, at 16:38, Charles Iliya Krempeaux wrote:
> I've been actually considering using a local HTTP server to implement
> things.  (Which is something you are doing too.)  Although I thought
> some extra "sugar" was warranted, to help with (user) usabiliy and
> developer usability.

We have added some sugar too.  For example, we have javascript  
available on our site that can detect whether Dijjer is present on  
the user's machine and redirect the user to a download page if it isn't.

> I skimmed through the stuff on dijjer.org, and I have a questions.
> Does digger pay attention to HTTP headers?  And act basically as a web
> cache?

Yes, we have attempted to stick as closely to the HTTP protocol as  
possible.

> For example, here's some (but not all) "rules" that I was planning on
> following.... If HTTP headers "say" that something should NOT be
> cached, then it should NOT be on the P2P network.

Yes, we obey the various HTTP no-cache headers.  We consider it  
important for Dijjer to act as much like a HTTP cache as possible so  
that we are afforded the protection the DMCA gives to caches for  
copyright infringement.

>   Stuff on the P2P
> network should be removed after the date for the "Expires" header
> passes?

We don't obey "Expires" explicitly, but since Dijjer pings the  
original web server each-time something is downloaded to ensure that  
the file is still there and hasn't changed, if it is removed from the  
web server, it will effectively be removed from Dijjer at the same  
instant.

> Things from non-HTTP GET methods should NOT be put onto the
> P2P network?  Etc.

We attempt to be smart about our interaction with HTTP, if there are  
shortcomings in this regard they will be easy to fix.

Ian.