Mq based Pipeline about wangle

[fugalh]

Conceptually it should be possible, yes. But there isn't code written for it yet. I think you'd need to implement the appropriate Handler subclass, i.e. see channel/Handler.h for the interface and channel/EventBaseHandler.h and channel/AsyncSocketHandler.h for examples/inspiration.

[crackcomm]

It may be useful to mention also bootstrap/ClientBootstrap.h for better understanding.

[BLaurent]

Ok,
I think I can do it, but I might need more advise.

For the handler I can see why I need to have one.

so for the Handler shall I create something like that :

class ZMQHandler : public wangle::Handler<  std::unique_ptr<folly::IOBuf>, zmq::message_t,
  zmq::message_t, std::unique_ptr<folly::IOBuf>> 

or Include the content of the message instead, replacing zmq::message_t by std::string for example.

zmq include several communication patterns, so I guess that what service is made for.
Mean that for Pub/Sub for example, I'll have publish service that will use the operator() for publishing message and the same on subscribe.

Second is topic filter I was thinking of adding a step to the pipeline to prefix message by a given prefix.
What do you think ?

Regards
Ben

[fugalh]

I think instead stacking on top of socket and dealing with a byte stream, this would be a terminal type (in place of socket) and let zmq do all the socket work.