wolfstudy commented on pull request #308: URL: https://github.com/apache/pulsar-client-go/pull/308#issuecomment-654952140
> 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. Sorry, @cckellogg About this, i don't think so. In what kind of scenarios, the user needs to write a message to the `MessageChannel`? > I'm confused by this what is replacing the message channel? As I said above, although we exposed MessageChannel, in more cases, we expect users to read data from this channel instead of writing data, so this parameter is exposed in consumer options Instead of producer's options. > The option needs to be read/write channel because the client needs to write messages. Yes, agree with you, but we can choose not to expose it to the outside world. ---------------------------------------------------------------- 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: us...@infra.apache.org
