cckellogg commented on pull request #308: URL: https://github.com/apache/pulsar-client-go/pull/308#issuecomment-654617633
I think the message channel option should remain because there are valid use cases for it. The option needs to be read/write channel because the client needs to write messages. When a user passes a message channel only the client should be writing to that channel. The documentation for the option is here // Sets a `MessageChannel` for the consumer // When a message is received, it will be pushed to the channel for consumption It seems clear to me that you should not write to this channel. We could add another statement saying you should not try to write to this channel? > I want to know in terms of functions, which operations are consumer.Chan() can not replace MessageChannel I'm confused by this what is replacing the message channel? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
