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

Redirect send2conn from sending to Hub to SvcConn #744

Merged
merged 1 commit into from
Nov 26, 2019

Conversation

terencefan
Copy link
Member

@terencefan terencefan commented Nov 25, 2019

We almost have all kinds of messages sending to our ServiceConnection directly in the existing codes.

Only sendToConnection will be sent to HubContext and I redirected it to ServiceConnection in this PR to fit the rules we are following now.

  • And also add an EchoHub for our ChatSample, which will let our customers doing their perf test easier.

@terencefan terencefan requested a review from vicancy November 25, 2019 08:56
@terencefan terencefan changed the title Redirect send2conn to SvcConn from Hub Redirect send2conn from sending to Hub to SvcConn Nov 25, 2019
@terencefan terencefan force-pushed the send2connection-refactor branch 3 times, most recently from 43f186a to cbbf551 Compare November 25, 2019 09:59
{
Assert.Equal("conn1", m.ConnectionList[0]);
Assert.Equal(1, m.Payloads.Count);
Assert.True(m.Payloads.ContainsKey(MockProtocol));
Copy link
Member

@vicancy vicancy Nov 26, 2019

Choose a reason for hiding this comment

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

MockProtocol [](start = 51, length = 12)

payloads should not contain blazor, use another name as MockProtocol?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, it should.
Our resolver supports 3 different protocols (including a mocked protocol "blazor"),
and this mocked protocol has been designated in the lifetime manager creation options.

@terencefan terencefan force-pushed the send2connection-refactor branch 3 times, most recently from 28e969d to 0dd5480 Compare November 26, 2019 03:45
@terencefan terencefan force-pushed the send2connection-refactor branch from 0dd5480 to fac0c19 Compare November 26, 2019 04:38
@terencefan terencefan merged commit ac7bb40 into Azure:dev Nov 26, 2019
@terencefan terencefan deleted the send2connection-refactor branch November 26, 2019 07:26
JialinXin pushed a commit to JialinXin/azure-signalr that referenced this pull request Dec 20, 2019
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.

2 participants