[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

     2

.. role:: raw-html(raw)

     3

   :format: html

     4

     5

RSS driven

     6

----------

     7

     8

RSS is a pretty useful technology that can be widely used on this

     9

site. Any set of data can be presented as RSS. You can then plug in

    10

an RSS reader into that and follow the site activity. For example :

    11

    12

:raw-html:`<p><a class="reference"

    13

href="view?vid=rss&amp;rql=Any+X%2CM+WHERE+X+modification_date+M+ORDERBY+M+DESC+LIMIT+30"><img

    14

alt="rss" src="data/rss.png"> latest changes</a></p>`