[repo] Add a publish/subscribe mechanism for inter-instance communication using zmq Each repo can have a publishing and any number of subscribing sockets whose addresses are specified in the instance's configuration. An application or cube can subscribe to some 'topics', and give a callback that gets called when a message matching that topic is received. As a proof of concept, this introduces a hook to clean up the caches associated with the repository when an entity is deleted. A subscription is added using Repository::zmq::add_subscription; the callback receives a list representing the received multi-part message as argument (the first element of the message is its topic).

     1

\.svn

     2

^build$

     3

^dist$

     4

\.pyc$

     5

\.pyo$

     6

\.bak$

     7

\.old$

     8

\~$

     9

\#.*?\#$

    10

\.swp$

    11

^doc/book/en/apidoc$

    12

\.old$

    13

syntax: regexp

    14

.*/data/database/.*\.sqlite

    15

.*/data/database/.*\.config

    16

.*/data/database/tmpdb.*

    17

^doc/html/

    18

^doc/doctrees/

    19

^doc/book/en/devweb/js_api/