cubicweb #2919297 drop zmq-pickle [resolved]
This pickle over zmq option have no real benefit over what pyro can already do.We are moving in the direction to drop such kind of pickled RPC. | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | 3.21.0 |
| load | 0.200 |
| load left | 0.000 |
| closed by | #ef3059a692cb Remove the remote repository-access-through-zmq support |
| patch | Remove leftover bits from start-repository command, and document its demise [applied]Remove the remote repository-access-through-zmq support [folded]Remove the remote repository-access-through-zmq support [applied] |
depends on
similar entities
dependency of
Comments
-
2013/06/04 06:23, written by agurney
-
2013/06/04 08:38, written by pydavid
add commentI'm confused. There's another ticket saying you want to drop pyro support too...
zmq-pickle has no advantage over pyro. And pyro have a lot of issue. zmq pickle have very few user and are therefor very easy to drop. dropping pyro is also something as wish, but it's a distinct step.