0.9.0pre3:
-* connections fail if transport-plugin/nat produces
- some addresses that don't work (enable 'use_localaddr' with bindto for example,
- so that some of the 'local' IPs do not work due to the bindto); the result
- seems to be that the plugin tries some of the broken addresses, fails and the
- transport-level connection never comes up.
-* Mantis:
- - 1694 --- try to reproduce (non-deterministic, w. testcase, need core/valgrind)
- - 1724 --- try to reproduce
- - 1725 --- try to reproduce (non-deterministic, w. testcase, need core)
- - 1728 --- investigate
- - 1736 --- investigate
- - 1737 --- investigate
-* clean buildbots
+* make sure transport provides latency in ATS (fs tests are complaining bitterly,
+ on line gnunet-service-fs_cp.c:338).
+* clean buildbots (with new transport)
0.9.0pre4:
-* NAT library: [CG/MW]
- - make code used by gnunet-setup asynchronous, add timeout (external-ip can hang!)
-* Transport:
- - integration of new NAT/plugin API with HTTP/HTTPS plugin
- - testing (again)
* GNUNET-GTK: [CG]
- figure out where in the GUI we should show active upload operations and allow aborts
- handle events:
+ search error
+ publish error
+* NAT:
+ - support HOSTNAME given for external-IP address (dyndns!)
* FS [CG]
- implement multi-peer FS performance tests + gauger them!
+ insert
+ download
+ search
+* transport:
+ - explicit DISCONNECT: add signature, create message...
+ - CONNECT: actually consider switching session...
0.9.0:
* new webpage:
- WLAN transport backend [DB]
- need to periodically probe latency/transport cost changes & possibly switch transport
(working ATS)
-* DATASTORE: [CG]
- - check indexes / SQL for performance
* DV:
- proper bandwidth allocation
- performance tests
we have not 'used' (for their public keys) in a while; need a way
to track actual 'use')
- make sue we also trigger notifications whenever HELLOs expire
-* NAT:
- - repeatedly resolve hostname and look up interfaces to determine our own IP
* WLAN:
- nice signal strength adjustment [MW]
- energy cost in ATS [MW]