The current implementation of mr4c provides a default HttpMessageHandler which provides plumbing to send messages to a registered topic URL. This works, and sends topic messages to the remote URL. [HttpMessageHandler](https://github.com/google/mr4c/blob/master/java/src/java/com/google/mr4c/message/HttpMessageHandler.java) There is currently no mechanism to receive any http messages via a same / similar route. The API is there `MessageConsumer` for which you implement `virtual void receiveMessage(const Message& msg)` However mr4c is missing a Http Message Handler for receiving messages, and sending them through to any registered MessageConsumers
The current implementation of mr4c provides a default HttpMessageHandler which provides plumbing to send messages to a registered topic URL.
This works, and sends topic messages to the remote URL.
HttpMessageHandler
There is currently no mechanism to receive any http messages via a same / similar route.
The API is there
MessageConsumerfor which you implementvirtual void receiveMessage(const Message& msg)However mr4c is missing a Http Message Handler for receiving messages, and sending them through to any registered MessageConsumers