Home » History » Version 47

Adrien Crivelli, 11/28/2008 12:54 PM

1 1 Greg Burri
h1. Home
3 3 Greg Burri
* [[Study of bittorent protocol]]
4 8 Greg Burri
* [[Study of UPNP]]
5 39 Greg Burri
* [[Study of UDP multicast]]
6 38 Greg Burri
* [[Study of Thrift]]
7 37 Greg Burri
* [[Study of Protocol Buffer]]
8 45 Greg Burri
* [[GUI]]
9 30 Greg Burri
* [[Protocols]]
10 3 Greg Burri
11 31 Greg Burri
h2. Brainstorming
12 4 Greg Burri
13 21 Greg Burri
* Core and GUI are independent. They communicate over TCP socket.
** It is possible to launch the core without the GUI. The core does not depend of any kind of graphic library.
** If the GUI crashes then the core remains.
16 22 Greg Burri
* Designed for LAN usage (full trusted peers and very high speed transfers).
17 37 Greg Burri
* Efficient (very low CPU usage).
18 18 Greg Burri
* Distributed download (multi peer downloading and no central server).
19 36 Greg Burri
** Quicker peer first. The speed of a peer is an average over a period of time say 5 min. The speed of an unknown peer is maximum thus it will be take first. If a downloading is too slow (like three time slower than the best known peer) then it can switch to a quicker free peer.
20 1 Greg Burri
** Rarest parts first.
21 37 Greg Burri
** A part can be resumed from any peer which own a complete copy.
** A file from a user is identified by its name and its folder.
23 1 Greg Burri
** Fixed part size (2^24 B = 16 MB) hashed with SHA-1. Used to control the integrity of parts and to identify each part. If the SHA-1 of a part does not match the given SHA-1 then it will be re-downloaded entirely.
24 44 Greg Burri
** The number of concurrent download is around 3 parts simultaneous but not more than 1 per peer. The number of concurrent upload is unlimited.
25 43 Greg Burri
** Recursive folder downloading.
** The paths of the files are recreated in the downloading peer.
27 40 Greg Burri
* There is a general chat. There is no private chat. The chat uses UDP multicast (if possible).
28 25 Greg Burri
* Multicast UDP for services discovering (maybe UPNP). Each peer announces periodically he is alive with a multicast message.
29 18 Greg Burri
* MDI GUI with GTK2HS.
30 1 Greg Burri
** A panel to view the current peers and their amount of sharing.
31 44 Greg Burri
** A window to view the current downloads (leechage) and one for the current uploads (seedage). These windows are very similar. The list is ordered, first the complete download then the current downloading files and finally the queued files.
32 40 Greg Burri
** A window for the chat.
33 39 Greg Burri
** Some windows for each file browsing. The files and folders are seen like a tree (like in the Finder of Mac OS X)
** Some windows for each file searching. The displayed list is identical to the browsing list.
35 18 Greg Burri
** A modal window for the settings.
*** The shared folders.
37 1 Greg Burri
*** The incoming folders (take the first if enough available space disk otherwise the second and so one..).
38 34 Greg Burri
*** Bandwidth and CPU limitation with a single option (checkbox).
39 42 Greg Burri
* Using of "Thrift": or "Protocol Buffers": for definition of the protocol between two peers and between the Core and the GUI.
40 1 Greg Burri
* File list with name+size.
41 39 Greg Burri
* Non blocking search, the list is dynamically filled for each peer answer.
42 1 Greg Burri
* Using of systray (optional).
43 39 Greg Burri
h3. Secondary ideas
46 18 Greg Burri
* Parse meta data like ID3tag when searching.
47 39 Greg Burri
* Graphics of the transfer rate over time.
* Free space management.
* Private chat
* Automatically detect a running game and set the limitation flag.
51 47 Adrien Crivelli
* Automatically detect CPU/bandwidth usage and set limitation flag.
52 46 Greg Burri
* Protect some sharing by a password