Project

General

Profile

Home » History » Version 73

Greg Burri, 12/05/2008 06:17 PM

1 1 Greg Burri
h1. Home
2
3 64 Greg Burri
* [[Development process]]
4
5
6 31 Greg Burri
h2. Brainstorming
7 4 Greg Burri
8 21 Greg Burri
* Core and GUI are independent. They communicate over TCP socket.
9 68 Greg Burri
** It's possible to launch the core without the GUI and without X launched under Linux.
10
** The core show, if its possible, an icon in the trayicon with a minimal menu to manage it.
11
** The core does not depend of any kind of graphic library except for the trayicon.
12 1 Greg Burri
** If the GUI crashes then the core remains.
13 68 Greg Burri
** It's possible to control the core remotely with a password.
14 22 Greg Burri
* Designed for LAN usage (full trusted peers and very high speed transfers).
15 37 Greg Burri
* Efficient (very low CPU usage).
16 18 Greg Burri
* Distributed download (multi peer downloading and no central server).
17 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.
18 65 Greg Burri
After A period of time without any download from a peer say 30min its speed is reseted to the maximum.
19 62 Greg Burri
** Rarest parts first. If there is no rarest parts then the choice is randomly.
20 37 Greg Burri
** A part can be resumed from any peer which own a complete copy.
21
** A file from a user is identified by its name and its folder.
22 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.
23 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.
24 43 Greg Burri
** Recursive folder downloading.
25
** The paths of the files are recreated in the downloading peer.
26 40 Greg Burri
* There is a general chat. There is no private chat. The chat uses UDP multicast (if possible).
27 69 Greg Burri
* Multicast UDP for services discovering (maybe UPNP). Each peer announces periodically (T) he is alive with a multicast message. If we doesn't receive any alive message from a peer while 3*T we consider it dead and we remove it from the list.
28 18 Greg Burri
* MDI GUI with GTK2HS.
29 1 Greg Burri
** A panel to view the current peers and their amount of sharing.
30 67 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 downloads then the uncomplete ones with 0 peers then the current downloading files and finally the queued files.
31 40 Greg Burri
** A window for the chat.
32 57 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).
33 39 Greg Burri
** Some windows for each file searching. The displayed list is identical to the browsing list.
34 18 Greg Burri
** A modal window for the settings.
35
*** The shared folders.
36 1 Greg Burri
*** The incoming folders (take the first if enough available space disk otherwise the second and so one..).
37 34 Greg Burri
*** Bandwidth and CPU limitation with a single option (checkbox).
38 42 Greg Burri
* Using of "Thrift":http://incubator.apache.org/thrift/ or "Protocol Buffers":http://code.google.com/apis/protocolbuffers/docs/overview.html for definition of the protocol between two peers and between the Core and the GUI.
39 1 Greg Burri
* File list with name+size.
40 73 Greg Burri
* Non blocking search, the list is dynamically filled for each peer answer. The search is active on files and folders name.
41 1 Greg Burri
* Using of systray (optional).
42 71 Greg Burri
* When you browse the files of someone you will see all its files with non-hashing files too.
43
** The hashing will be created and sent when you decide to download a specific file.
44
* Support of UTF-8.
45 66 Greg Burri
** Creating many tests with special characters in the name of the files or directories
46
** Maybe use of 'Distribution.Simple.Utils.toUTF8'
47 61 Greg Burri
* "Haskell":http://www.haskell.org language
48
** A polymorphically statically typed, lazy, purely functional language. Very high level modern language.
49
** Open source.
50
** Efficient.
51
** Good GTK-Binding : http://www.haskell.org/gtk2hs/
52 1 Greg Burri
53
h3. Secondary ideas
54
55 72 Greg Burri
* The users can add some comments or tags associated to theirs sharing. These comments or tags are displayed in the list of peers (new column ? tooltip ?).
56 1 Greg Burri
* Parse meta data like ID3tag when searching.
57
* Free space management.
58
* Private chat.
59 70 Greg Burri
* Multi languages.
60 1 Greg Burri
* Automatically detect a running game and set the limitation flag.
61
* Automatically detect CPU/bandwidth usage and set limitation flag.
62
* Protect some sharing by a password / user rights for shares.
63
* Statistics window with graphs.
64 60 Greg Burri
65
h2. Functional
66
67
* [[Functional constraints]]
68
* [[GUI]]
69
* [[Logo]]
70
71
h2. Technical
72
73
* [[Study of the BitTorrent protocol]]
74
* [[Study of UPNP]]
75
* [[Study of UDP multicast]]
76
* [[Study of Thrift]]
77
* [[Study of Protocol Buffer]]
78 63 Greg Burri
* [[Libraries]]
79 60 Greg Burri
* [[Protocols]]
80
* [[Prototypes]]
81
* [[Guidelines]]