X-Git-Url: http://git.meshlink.io/?p=meshlink;a=blobdiff_plain;f=TODO;h=6a51375cd83353cbfae3ed66762318b7b32fb23e;hp=3d0a7c8c637cce76437a8752f521b57bf1410fc0;hb=ed210eb557e7fb5edbac89ff43a573ae84a941f9;hpb=ffc79bcd20b2b8085c906a446318817808bc36ae

diff --git a/TODO b/TODO
index 3d0a7c8c..6a51375c 100644
--- a/TODO
+++ b/TODO
@@ -1,15 +1,41 @@
-Things left to do to make cabal superstable:
---------------------------------------------
- * Check for connection loops. Inter-daemon
-   connections should always satisfy the
-   tree property.
- * Check for duplicates. If there's a
-   timeout and a host reconnects before the
-   old connection is closed, duplicate
-   entries appear in every connection list.
- * Redundancy: multiple ConnectTo lines, if
-   one fails others might be tried.
- * Persistence: don't quit when no connection
-   can be made directly after start of the
-   daemon.
+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.