Initial client library rewrite, connects to remote server already.

[silc.git] / lib / silcclient / README

diff --git a/lib/silcclient/README b/lib/silcclient/README
index fef8dd769fef487af0e3cf8177a973fb4b496d6c..a9c9d485bf64d21034f256db6f7d59e788607944 100644 (file)
--- a/lib/silcclient/README
+++ b/lib/silcclient/README
@@ -61,8 +61,7 @@ Using FSM
    set the old SilcPacket to the packet thread's state context and move back
    to the packet processor with silc_fsm_next and silc_fsm_continue_sync
    (always synchronously, never async).  This design may change later,
-   but for now this is it.  This also means that SILC_FSM_CALL must not
-   be used in packet processors because it returns SILC_FSM_WAIT.
+   but for now this is it.
 
 
 When to use FSM semaphore signalling?