-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fill in Publish / Request Header Gaps #839 #738
Conversation
/// <param name="msg">A <see cref="Msg"/> instance containing the subject, optional reply, and data to publish | ||
/// to the NATS server.</param> | ||
/// <seealso cref="IConnection.Publish(string, byte[])"/> | ||
void Publish(Msg msg); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is just moved lower down for organizational purposes
/// <param name="timeout">The number of milliseconds to wait.</param> | ||
/// <returns>A <see cref="Msg"/> with the response from the NATS server.</returns> | ||
/// <seealso cref="IConnection.Request(Msg)"/> | ||
Msg Request(Msg message, int timeout); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is just moved up for organizational purposes
Is there a request for this? It is convenient but the API footprint if getting large with all of the overloads. In the past I nudged users toward msg API if they needed to use headers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per direct discussions, the API footprint addition falls into an ease of use feature so it a positive imo. LGMT.
addressing #736