cubicweb #2919295 deprecate 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.19.3 |
| load | 0.500 |
| load left | 0.000 |
| closed by | #57e2cffa6329 Add warning messages when enabling remote pickle-based repository access |
| patch | Add warning messages when enabling remote pickle-based repository access [applied] |
dependency of
Comments
-
2013/06/03 16:10, written by acampeas
-
2013/06/03 16:18, written by pydavid
add commentWhat replacement do you propose for the currently provided functionality ?
Short term I recommend using direct pyro connection instead of zmq-pickle.
On the long run I would like to see the current dbapi dropped in favor of using REST interface or simple RQL server over zmq.