Remove obsolete paragraph about the need for a second connection

Due to the event-based handling of incoming data from i3 we do not
suffer from this problem.

diff --git a/lib/AnyEvent/I3.pm b/lib/AnyEvent/I3.pm
index 310fa5efe65321d3c540a224d9a8c91da3006273..d763357cf412d46bbad12c3fc5db1f5ad77e8139 100644 (file)
--- a/lib/AnyEvent/I3.pm
+++ b/lib/AnyEvent/I3.pm
@@ -27,10 +27,6 @@ This module connects to the i3 window manager using the UNIX socket based
 IPC interface it provides (if enabled in the configuration file). You can
 then subscribe to events or send messages and receive their replies.
 
-Note that as soon as you subscribe to some kind of event, you should B<NOT>
-send any more messages as race conditions might occur. Instead, open another
-connection for that.
-
     use AnyEvent::I3 qw(:all);
 
     my $i3 = i3("/tmp/i3-ipc.sock");