You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/05/10 18:09:51 UTC

[GitHub] [pulsar-dotpulsar] JarrodJ83 commented on issue #39: Reading Incoming Message Properties

JarrodJ83 commented on issue #39:
URL: https://github.com/apache/pulsar-dotpulsar/issues/39#issuecomment-626366802


   Thanks @blankensteiner I had not seen that. That will get me what I need I believe. Out of curiosity, is there are a particular reason why on the consumer side everything is done through `DotPulsar.Message` but on the producer side things are separated out between the data and the metadata? Do you think there would be any benefit in making the producers and consumers both leverage the same objects? It may make it a little more consistent in this case where you have to look different places for the props depending on if you are consuming or publishing. Just a thought. If it is something that sounds interesting to you I'd love to take a stab at it.


----------------------------------------------------------------
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:
users@infra.apache.org