leap_pycommon.git/src/leap, branch release/0.5.x [leap_pycommon] [pkg] update to versioneer 0.16 2016-04-01T21:33:26+00:00 Kali Kaneko kali@leap.se 2016-04-01T21:33:26+00:00 334fe8d2d38466ad309e1214d003f977f603dfb9 






[doc] update event annotation
2016-03-24T17:59:28+00:00

Kali Kaneko
kali@leap.se

2016-03-24T13:24:37+00:00

9365e03b6490e0b86ddde0fe35854431bf17d94c












[bug] close TxAuthenticator properly
2016-03-16T16:12:24+00:00

Christoph Kluenter
ckluente@thoughtworks.com

2016-03-16T16:03:52+00:00

3a317f04bfa55698a7064ea3d5c5a1b4cc5ead36

otherwise the context.term() does not return





otherwise the context.term() does not return







[feature] HookableService
2016-03-11T19:33:18+00:00

Kali Kaneko
kali@leap.se

2016-03-02T15:53:50+00:00

ecf025e3d6065c9729ac72489efcdc0218fdffe1

ad-hoc register/trigger mechanism used for service composition.
to be used in bitmask.core and bitmask.bonafide in the first place.





ad-hoc register/trigger mechanism used for service composition.
to be used in bitmask.core and bitmask.bonafide in the first place.







[style] pep8
2016-03-09T14:48:23+00:00

Kali Kaneko
kali@leap.se

2016-03-09T14:48:23+00:00

07dff4d010b284d8d46eb3b8a859083013c7441f












[tests] adapt events tests to recent changes
2016-02-29T23:39:43+00:00

Kali Kaneko
kali@leap.se

2016-02-29T23:33:28+00:00

027ad7eed50947608738ce0009fccf776936e55c












[feature] reactor-based authenticator
2016-02-29T14:32:24+00:00

Kali Kaneko
kali@leap.se

2016-02-23T23:28:05+00:00

24977b744b42df912a23a2861453e7d4d5202310

We don't really need a thread to make use of the ZAP authenticator.
Document bug fix after authenticator thread is gone





We don't really need a thread to make use of the ZAP authenticator.
Document bug fix after authenticator thread is gone







[bug] avoid the events server to block twistd daemon
2016-02-23T23:32:20+00:00

Kali Kaneko
kali@leap.se

2016-02-22T23:26:45+00:00

b940cfc29b88374ce57b101a39bc012bb903f6e8

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.





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.







[feature] optional flag to disable curve authentication
2016-02-22T23:25:21+00:00

Kali Kaneko
kali@leap.se

2016-02-22T23:25:21+00:00

88941164243ce1ac6f30c790120165c04ea4a041












[feat] Get events working on windows
2016-02-18T17:21:24+00:00

meskio on windows
meskio@leap.se

2016-02-11T10:26:06+00:00

a36fdc8ebec9c42c61a2c733ea280a3fa9103598

Always use tcp channels and disable curve encryption on the zmq
connections.

- Closes: #7899, #7239
- Related: #7919





Always use tcp channels and disable curve encryption on the zmq
connections.

- Closes: #7899, #7239
- Related: #7919