Handle incoming events from client

[Rishygunjal]

Hi team,

Really impressed with the work the team has done. I wanted to enquire about the handling of incoming events from client. In grpc_handlers.go, only two cases (topic subscription and topic unsubscription) have been handled, we need to be able to do handling of events as well from the client.

[Abhishekvrshny]

@Rishygunjal Yes, that's a valid point. Incoming events from the client are not yet handled. Would you like to add support for that feature?

[Rishygunjal]

@Abhishekvrshny Yes, I would love to connect and discuss my approach and the requirements for this package.

Feel free to reach out via email if you'd prefer to continue this discussion privately - rishygunjal@gmail.com

[Rishygunjal]

Hi @Abhishekvrshny , By researching and ideating , I have came up with the following ideas. I can add support for client → backend and client → client event delivery via the existing Propeller gRPC Channel() stream. The current implementation only supports backend → client messages (plus control requests like topic subscriptions). This change enables full bi-directional event flow while preserving reliability, acknowledgements, and metadata integrity. I am proposing the following changes:

• Inbound ChannelEvent handling in grpc_handler.go to process application-level messages sent from clients.

• Routing to backend via:

  • Existing NATS/Redis Pub/Sub for asynchronous consumption, or
  • Optional direct gRPC/HTTP sink for real-time processing.

• Delivery acknowledgements for client-originated events.

• Topic-based client-to-client messaging: Clients can send events to custom topics, and all other subscribed clients will receive the event through Propeller without requiring a backend hop.

Benefits

• Enables true bi-directional communication between clients and backend via Propeller.
• Facilitates real-time client-to-client interactions through topic subscriptions.
• Maintains existing reliability guarantees and delivery semantics.
• Flexible backend integration options (Pub/Sub, direct gRPC, or HTTP).

Please let me know what you think about it. Thanks!

[Abhishekvrshny]

Hi @Rishygunjal , this looks like a good plan at a high level. Would you like to file a draft PR? Low level nuances can be discussed as part of that

[Rishygunjal]

Hi @Abhishekvrshny , I have added a Draft PR named - Feature/client event handling #81. You can check it out and let me know what you think

[Abhishekvrshny]

Thanks @Rishygunjal . Please give me some time. I will review and get back

[Rishygunjal]

Hi @Abhishekvrshny, did you get a chance to take a look at the same? I would love to contribute more if you require any further changes.