We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When providing a record using ds.record.listen(), if:
ds.record.listen()
a remote client subscribes to the record, triggering a subscribe on the provider and
the provider subscribes to the record locally and
the remote client unsubscribes
then:
the provider's record subscription triggers a resubscribe on the listen callback and
the provider receives the error message: Error: UNSOLICITED_MESSAGE: foo/bar (R)
Error: UNSOLICITED_MESSAGE: foo/bar (R)
No error is logged on the server
What should happen:
The provider's record subscription is ignored.
This issue first occurred in master in commit e7eea7c and affects releases: v2.1.0, v2.1.1, v2.1.2
The referenced commit includes a fix for issue #476
The text was updated successfully, but these errors were encountered:
6036471
Fixes #531 unsolicitated message when all clients unsubscribe
912767e
Merge pull request deepstreamIO#531 from jaime-ez/master
e8769c0
[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle
yasserf
No branches or pull requests
When providing a record using
ds.record.listen()
, if:a remote client subscribes to the record, triggering a subscribe on the provider and
the provider subscribes to the record locally and
the remote client unsubscribes
then:
the provider's record subscription triggers a resubscribe on the listen callback and
the provider receives the error message:
Error: UNSOLICITED_MESSAGE: foo/bar (R)
No error is logged on the server
What should happen:
The provider's record subscription is ignored.
This issue first occurred in master in commit e7eea7c
and affects releases: v2.1.0, v2.1.1, v2.1.2
The referenced commit includes a fix for issue #476
The text was updated successfully, but these errors were encountered: