2 ms·
RQ never publishes a real protocol for sending and receiving jobs. Also the `data` field could be anything because it's pickled so you could send a whole Python
by thangngoc89 2y ago
RQ never publishes a real protocol for sending and receiving jobs. Also the `data` field could be anything because it's pickled so you could send a whole Python's object there.
See [1] for efforts to make RQ cross language compatible
[1] https://github.com/rq/rq/issues/1808 https://github.com/rq/rq/issues/1808
- SideburnsOfDoom 2y ago> RQ never publishes a real protocol for sending and receiving jobs. Then, RQ sounds substandard. > Also the `data` field could be anything "the sender could send anything" is true in theory, but in practice it is both useless and false. If you want to make it work, sender and receiver need to agree on a lot. JSON could take any forms too, but the sender and receiver have to typically agree, implicitly or explicitly, on many of the details of the message. Like, what fields are needed, what the allowable values are, etc.