summaryrefslogtreecommitdiff
path: root/src/leap/common/events/txclient.py
AgeCommit message (Collapse)Author
2016-02-29[tests] adapt events tests to recent changesKali Kaneko
2016-02-29[feature] reactor-based authenticatorKali Kaneko
We don't really need a thread to make use of the ZAP authenticator. Document bug fix after authenticator thread is gone
2016-02-23[bug] avoid the events server to block twistd daemonKali Kaneko
1. refactor the zmq_connect/bind methods to use the txzmq addEndpoints mechanism, which cleans up the code a bit. it uses the underlying bindOrConnect method. 2. wrap the addEndpoints call in a helper function that ensures that doRead is called afterward. I'm not fully comfortable with us still using the AuthenticatorThread, I believe we could go witha txzmq-based authenticator for curve.
2015-10-07[bug] consider STANDALONE for the pathsIvan Alejandro
Since we need to write a file we have to consider whether we are running in 'standalone' mode or not to use the right path prefix. - Related: #7512
2015-09-16[refactor] move checking flag to main moduleKali Kaneko
2015-09-16[tests] Make txclient honor flags.EVENTS_ENABLEDFolker Bernitt
- Breaks tests in dependent repos like soledad otherwise, because server.key could not be found
2015-07-21[feature] add global flag for disabling the events frameworkKali Kaneko
this will be used to allow the unittests to disable the events framework. this way, emit() will become a passthrough. note that, until now, the basetest class is making use of the threaded version of the client, which launches a zmq tornado-based ioloop. this is wrong, and will have to be addressed in a future commit. we'll have to make use of the global EVENTS_ENABLED flag in the txclient version when those changes are made. Related: #7259 Relases: 0.4.2
2015-06-26[bug] run callback from thread in events clientdrebs
2015-05-27[feat] refactor events to use ZMQdrebs
Before this commit, protobuf and protobuf.socketrpc were used to serialize and transmit messages between events clients. This change implements a simpler ZMQ client/server events mechanism that uses ZMQ sockets for transmitting messages from clients to server and to redistribute such messages to subscribed clients. Closes: #6359