summaryrefslogtreecommitdiff
path: root/src/leap/common/events/README.rst
diff options
context:
space:
mode:
authordrebs <drebs@leap.se>2013-07-24 14:01:30 -0300
committerdrebs <drebs@leap.se>2013-07-24 15:36:21 -0300
commit1f1412f3c31dfba10135ceae4641313ee48318c8 (patch)
tree895e62b4a9d2a3e1b1e4da7c506b8ceda374b622 /src/leap/common/events/README.rst
parentf659de6e98073dc738b8d245e0ddb897f5bd3779 (diff)
Refactor events so components become clients.
Diffstat (limited to 'src/leap/common/events/README.rst')
-rw-r--r--src/leap/common/events/README.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/src/leap/common/events/README.rst b/src/leap/common/events/README.rst
index 813be8b..2e7f254 100644
--- a/src/leap/common/events/README.rst
+++ b/src/leap/common/events/README.rst
@@ -1,19 +1,19 @@
Events mechanism
================
-The events mechanism allows for "components" to send signal events to each
-other by means of a centralized server. Components can register with the
+The events mechanism allows for clients to send signal events to each
+other by means of a centralized server. Clients can register with the
server to receive signals of certain types, and they can also send signals to
-the server that will then redistribute these signals to registered components.
+the server that will then redistribute these signals to registered clients.
Listening daemons
-----------------
-Both components and the server listen for incoming messages by using a
+Both clients and the server listen for incoming messages by using a
listening daemon that runs in its own thread. The server daemon has to be
-started explicitly, while components daemon will be started whenever a
-component registers with the server to receive messages.
+started explicitly, while clients daemon will be started whenever a
+client registers with the server to receive messages.
How to use it