-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Dorman wanted us to know:
>> > Could we get some kind of p2p solution up and running? With so many >> > people wanting to keep a local cooker tree, it would seem self-evident >> This would be could, someone could investigate on that topic? >Warly, I volunteer! I'd like to co-ordinate at least. I'll to set up a >CookerP2P project if that is something that people would like to see (and >preferably endorsed by the Mandrake developers!). Shall I use Sourceforge, or >something else? I think SF is the way to go yes. >I invite people interested in a CookerP2P app to email me, so I can notify >them when things are moving. Suggestions and offers of help are very welcome >of course! Consider this my letter of intent to be a tester, I doubt I could do much more than that. As for suggestions, there is a bittorrent c library project on sf named libbt: http://sourceforge.net/projects/libbt/ It's still very early in the development, but it looks like it supports the basic functions. Now to devise a way of handling: 1) an entire tree of files/directories 2) when a file changes mid-stream Item #1 will have to be handled with mods to the structure of the bittorrent itself and some intelligence for filesystem traversal. Item #2 will have to be handled with the invention of some form of message passing from master to clients to indicate that the bittorrent should be resynced (but it should not be an outbound connection, rather, the master waits for clients to check in with their status and then tells them that the torrent needs to be resynced). I have visions of using rsync functions to resync the torrents, then bittorrent functions to sync individual files. Note that some form of caching or indexing really should be used as well because the amount of filesystem thrashing when a 100 clients all ask for segments of different files will be extreme and on ALL clients, not just the server. Alternatively, use a two tier system where the first tier is a single bittorrent to keep everybody's tree defining torrents in sync with the master. Then the second tier is running from that synced torrent. I also suggest that we not tie this to Mandrake or Cooker, but try to make it a general mirroring solution (at least for anybody not behind a NAT'ing firewall that they don't have the ability to forward the required ports to their machine). - -- Blue skies... Todd http://www.mrball.net Public key: http://www.mrball.net/todd.asc There are only 10 types of people in this world. Those who understand binary and those who don't. Linux kernel 2.4.21-0.25mdk 8 users, load average: 0.03, 0.07, 0.08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE/R+GcIBT1264ScBURAiM4AJ0ToVMKms2tlzC/LbV8ARDhlofpYACglEwD YNW9LPESUDt3sVwbZg9dqUQ= =rk92 -----END PGP SIGNATURE-----
