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

add possibility to filter listen event on server #32

Closed
Vitaliy-Yarovuy opened this issue Dec 30, 2013 · 5 comments · Fixed by #51
Closed

add possibility to filter listen event on server #32

Vitaliy-Yarovuy opened this issue Dec 30, 2013 · 5 comments · Fixed by #51
Labels
Milestone

Comments

@Vitaliy-Yarovuy
Copy link

some thing like that:

socket.on('my/todos updated', { ids:[1,2,3], maxLenght: 200 }, function(todo) {
    console.log('Got an updated Todo!', todo);
});
@Vitaliy-Yarovuy
Copy link
Author

and can you look issues that closed, but I have add some additional comment
#31

@daffl
Copy link
Member

daffl commented Dec 30, 2013

Yes, I've been thinking about how to do this properly, too. Debating of adding an event dispatching mechanism where you can decide if the event + object combination should be sent to a connected client.

@daffl
Copy link
Member

daffl commented Mar 28, 2014

Following up on it here: #44 (comment)

@daffl
Copy link
Member

daffl commented Apr 6, 2014

Pull requests #50 and #51 add this filter functionality and should land in a release probably some time next week.

@daffl daffl closed this as completed in #51 Apr 8, 2014
daffl pushed a commit that referenced this issue Aug 21, 2018
* chore(package): update primus to version 6.0.5

* Update Primus compatibility

* Switch to UWS for testing

* Add missing dependency
daffl pushed a commit that referenced this issue Aug 22, 2018
* chore(package): update primus to version 6.0.5

* Update Primus compatibility

* Switch to UWS for testing

* Add missing dependency
daffl pushed a commit that referenced this issue Aug 25, 2018
updating error handler to be more HTML friendly
daffl added a commit that referenced this issue Aug 25, 2018
daffl added a commit that referenced this issue Aug 28, 2018
* Update to Feathers v3

* Prepare prerelease

* Revert verifier
daffl pushed a commit that referenced this issue Aug 28, 2018
* fix(package): update passport-jwt to version 3.0.0

* Compatibility with passport-jwt 3.0

* Remove package-lock.json, will be added later

* Add package-lock.json back
daffl added a commit that referenced this issue Aug 29, 2018
* Fix header casing

* Fix test cases and Readme
daffl added a commit that referenced this issue Aug 29, 2018
* Update to Feathers v3

* Prepare prerelease

* Revert verifier
daffl pushed a commit that referenced this issue Aug 29, 2018
* fix(package): update passport-jwt to version 3.0.0

* Compatibility with passport-jwt 3.0

* Remove package-lock.json, will be added later

* Add package-lock.json back
daffl added a commit that referenced this issue Aug 29, 2018
* Fix header casing

* Fix test cases and Readme
@lock
Copy link

lock bot commented Feb 8, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants