Hmm, that would be a problem especially if your WebSocket clients can come
and go.
I am actually wondering if your WebSocket is needed for any other usage
beside this? If not, then you may probably get rid of the server and just
let all clients directly consume from Kafka, where each one of them
m
Hi Guozhang,
Thanks for your input. That would be a great solution if it wasn't that
more than one client could be connected via WebSocket. Hence, a single
client can only tell what they've consumed and the consumer is shared for
everyone connected.
Is there any other way I can go about this prob
Hi Kevin,
The current high-level Scala consumer does not have a rewind function but
if the other client is able to notify you through WebSocket periodically as
long as it is not disconnected, then what you can do is let your Java app
to buffer messages even after pushing them to the WebSocket, and
Thanks for the link, Sharninder. I'm not entirely sure this is what I'm
looking for. I do not know whether or not the client actually received the
messages or not.
The Java-application consumes the messages from Kafka and then push them to
Pusher (https://pusher.com/). The client, connected to the
> I have a backend service written in PHP. This service pushes messages to
> Apache Kafka (over the topic "posts") when posts are created, read and
> removed. I also have a backend service written in Java. This service
> consumes messages from Apache Kafka (for the "posts" topic) and push them
> ou
Hi everyone!
This is my first post in the mailing list, so bear with me.
I have a backend service written in PHP. This service pushes messages to
Apache Kafka (over the topic "posts") when posts are created, read and
removed. I also have a backend service written in Java. This service
consumes me
