Can't use MessageSender & MessageReceiver about azure-service-bus-dotnet

[jtaubensee]

Also, a reminder to rename the Peek() operation to Browse() in order to avoid confusion between that and PeekLock mode.

[binzywu]

Hi @SeanFeldman, could you please elaborate a little more about the scenarios that you will need this?

[SeanFeldman]

Absolutely @binzywu
When a process is receiving messages, it handles messages from queues and subscriptions. The process doesn't differentiate the entity type messages come from as messages contain information required for proper processing. Same is applied for sending, messages are sent out using a path, w/o differentiating if destination is a topic or a queue.

With both MessageSender and MessageReceiver abstract it is not possible with the new client.

[binzywu]

@SeanFeldman, @nemakam will be working on this.

[SeanFeldman]

👍 @binzywu
I'll be following the PR the moment it shows up.

[nemakam]

You can track the changes in PR #82

[jtaubensee]

Closing in favor of #87

[nemakam]

Reopening the issue since MessageSender and MessageReceiver are made internal in #87 .

[SeanFeldman]

👎 for Browse.
Peek is a well established term for the operation and means exactly what it does. Not to mention that other messaging and queueing technologies use the same nomenclature.

[jtaubensee]

Closing based on #146