Skip to content
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

Idle-Timeout communicated in open frame #239

Merged
merged 2 commits into from
Nov 29, 2017
Merged

Idle-Timeout communicated in open frame #239

merged 2 commits into from
Nov 29, 2017

Conversation

zmhh
Copy link
Contributor

@zmhh zmhh commented Nov 29, 2017

No description provided.

@zmhh
Copy link
Contributor Author

zmhh commented Nov 29, 2017

Related to #238

@zmhh
Copy link
Contributor Author

zmhh commented Nov 29, 2017

Also includes change to heartbeat frequency based on idle timeout parameter received. Now sets heartbeat frequency to half of timeout, as suggested in AMQP spec. Previously 3000 ms were subtracted. This could be an issue for low timeouts and with connections with high latency (if it takes more than 3s to send the heartbeat over the wire). Communicating at half of the idle timeout removes these issues and gives the developer more control.

@zmhh zmhh mentioned this pull request Nov 29, 2017
@@ -70,7 +70,7 @@ public int MaxLinksPerSession
/// <summary>
/// Gets or sets the open.idle-time-out field.
/// </summary>
public int IdleTimeout
public uint IdleTimeout
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A property type change is potentially a breaking change so let's keep it as int. In OnOpen there is max value check so it should be able to handle any received idle timeout value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants