VooDoo
DavidXanatos (Talk | contribs) |
DavidXanatos (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | The ''VooDoo'' ,UniversalPartfileInterface, enables a slave client to work without having the content files. The client accesses the files of its master through the LAN. | + | The ''VooDoo'' ,UniversalPartfileInterface, enables a slave client to work without having the content files. The client accesses the files of its master through the LAN.<br> |
| + | The slave client has full upload/download capabilities and the gap list is updated every time when the master client gets new file data into the buffer. The slaves can share normal files aside from the voodoo files generally without interference.<br> | ||
| + | The feature is from the UL/DL code side linked to LanCast but it don’t requires it in any way, there is an optional extension that allows clients to search the LAN for usable slaves or masters.<br> | ||
| + | The connectivity of Voodoo Nodes can be restricted by using a Plaintext Password as well as by selective IP blacklisting, however since the socket accepts only connections from the LAN and Local Host this security measures are sufficient.<br> | ||
| + | <br>This feature is universal and, due to the very generic design of the interface, the Shared files can be accessed by any other file sharing client that supports the VooDoo protocol. With a modified BitTorrent client, you can download the same file from both networks. It is only necessary to associate a torrent with an ED2K hash ID. Other network support is so easy like the one above.<br> | ||
| + | The clients are working near to completely independent, so that you could run normal clients side-by-side. But you don’t waste HD space, because there is always only one real copy of the file.<br> | ||
| + | You can use VooDoo to bind two or more Internet connections to work on only one set of shared files. The feature is also usefully if you have a MAN (Metropolitan Area Network) where you limit one client to connect only to nodes inside the MAN and the other client only to nodes outside in the Internet. | ||
| − | |||
| − | |||
| − | |||
Invented by: Xanatos | Invented by: Xanatos | ||
Revision as of 10:22, 17 September 2007
The VooDoo ,UniversalPartfileInterface, enables a slave client to work without having the content files. The client accesses the files of its master through the LAN.
The slave client has full upload/download capabilities and the gap list is updated every time when the master client gets new file data into the buffer. The slaves can share normal files aside from the voodoo files generally without interference.
The feature is from the UL/DL code side linked to LanCast but it don’t requires it in any way, there is an optional extension that allows clients to search the LAN for usable slaves or masters.
The connectivity of Voodoo Nodes can be restricted by using a Plaintext Password as well as by selective IP blacklisting, however since the socket accepts only connections from the LAN and Local Host this security measures are sufficient.
This feature is universal and, due to the very generic design of the interface, the Shared files can be accessed by any other file sharing client that supports the VooDoo protocol. With a modified BitTorrent client, you can download the same file from both networks. It is only necessary to associate a torrent with an ED2K hash ID. Other network support is so easy like the one above.
The clients are working near to completely independent, so that you could run normal clients side-by-side. But you don’t waste HD space, because there is always only one real copy of the file.
You can use VooDoo to bind two or more Internet connections to work on only one set of shared files. The feature is also usefully if you have a MAN (Metropolitan Area Network) where you limit one client to connect only to nodes inside the MAN and the other client only to nodes outside in the Internet.
Invented by: Xanatos
To find in: NeoMule
