Avoid allocating packet buffers unnecessarily.

[meshlink] / TODO

diff --git a/TODO b/TODO
index 226e2713749327b476254c2b9db72e30d9a616fe..6a51375cd83353cbfae3ed66762318b7b32fb23e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,27 +1,41 @@
-TODO LIST
-
-Goals for 1.0 release:
-
-* Check Solaris port
-* Check FreeBSD port again
-* Check TCPonly and IndirectData
-
-* Check different linux architectures (x86, alpha and sparc32 done)
-* Store private key in a separate file (done, 1 dec 2000)
-* Sanity checks on configuration directory (mostly done)
-* Use efficient tree algorithms instead of linked lists (done)
-* Reenable queues for delayed packets (done)
-* Merge documentation files (SECURITY, INSTALL, PROTOCOL) into tinc.texi (done)
-* Different authentication scheme (done)
-* Add randomness to packet headers and PING/PONG requests (done)
-
-Goals for future releases:
-
-* Compression
-* Routing by MAC/switching (allows for more than only IPv4)
-* Broadcast/multicast
-* Windowing, chaffing, scattering, background noise
-* ABC protocol (superscalabilty)
-* Proxy ARP
-* Easy setup scripts (graphical?)
-* Threading
+TODO list for MeshLink
+----------------------
+
+* meshlink_join():
+  - add checks that we only join another mesh if we did not connect to any other node before.
+  - only allow meshlink_join() when the library thread is not running.
+  - remove old host config file if the invitation gave the node a different name.
+  - how to handle nodes that are part of one mesh and want to join another?
+
+* meshlink_leave()?
+  - leaving a mesh is basically starting all over again, with new private keys?
+
+* Allow meshlink_open() to be called with a NULL name, in anticipation of meshlink_join().
+  - Do not allow meshlink_start() if no Name is set.
+
+* Add autoconf/automake stuff to call Doxygen.
+
+* Write a manual
+  - Add introduction and walkthrough how to use MeshLink in an application to
+    the doxygen manual.
+  - Explain what MeshLink does and how it should be used in the application
+  - Import examples into the manual?
+  - List possible ways of synchronisation between application and library threads
+    - simple polling
+    - pthread_cond?
+    - pipe() to signal an event loop of the application's choice
+    - whatever equivalent(s) there are on Windows
+
+Not finished but being worked on:
+---------------------------------
+
+* Provide thread-safety to functions that return pointers to meshlink_node_t.
+  - The mesh->nodes tree can be updated by the library thread at any time,
+    so it must be protected by a mutex or rwlock.
+  - Individial node_t's must never be freed or moved except in meshlink_close().
+  - Check all public API functions.
+
+* Write a test suite for the library.
+
+* Add a "channel" library to MeshLink.
+  - Support multiple TCP- and UDP-like streams between two nodes.