[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

function datetuple(d) {

     2

    return [d.getFullYear(), d.getMonth()+1, d.getDate(), 

     3

	    d.getHours(), d.getMinutes()];

     4

}

     5

     6

function pprint(obj) {

     7

    print('{');

     8

    for(k in obj) {

     9

	print('  ' + k + ' = ' + obj[k]);

    10

    }

    11

    print('}');

    12

}

    13

    14

function arrayrepr(array) {

    15

    return '[' + array.join(', ') + ']';

    16

}

    17

    18

function assertArrayEquals(array1, array2) {

    19

    if (array1.length != array2.length) {

    20

	throw new crosscheck.AssertionFailure(array1.join(', ') + ' != ' + array2.join(', '));

    21

    }

    22

    for (var i=0; i<array1.length; i++) {

    23

	if (array1[i] != array2[i]) {

    24

    25

	    throw new crosscheck.AssertionFailure(arrayrepr(array1) + ' and ' + arrayrepr(array2)

    26

						 + ' differs at index ' + i);

    27

	}

    28

    }

    29

}