-
Notifications
You must be signed in to change notification settings - Fork 103
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
Conversation
43f186a
to
cbbf551
Compare
test/Microsoft.Azure.SignalR.Tests/ServiceLifetimeManagerFacts.cs
Outdated
Show resolved
Hide resolved
{ | ||
Assert.Equal("conn1", m.ConnectionList[0]); | ||
Assert.Equal(1, m.Payloads.Count); | ||
Assert.True(m.Payloads.ContainsKey(MockProtocol)); |
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.
MockProtocol [](start = 51, length = 12)
payloads should not contain blazor
, use another name as MockProtocol
?
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.
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.
28e969d
to
0dd5480
Compare
0dd5480
to
fac0c19
Compare
We almost have all kinds of messages sending to our
ServiceConnection
directly in the existing codes.Only
sendToConnection
will be sent toHubContext
and I redirected it toServiceConnection
in this PR to fit the rules we are following now.EchoHub
for ourChatSample
, which will let our customers doing their perf test easier.