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

allow .register(/wildcard/) #45

Open
kianenigma opened this issue Mar 15, 2017 · 3 comments
Open

allow .register(/wildcard/) #45

kianenigma opened this issue Mar 15, 2017 · 3 comments

Comments

@kianenigma
Copy link
Member

kianenigma commented Mar 15, 2017

overall, our path based is better than pattern matching (bullshit) (is it really? 🤔 )

try and justify this!

@kianenigma kianenigma self-assigned this Mar 15, 2017
@kianenigma
Copy link
Member Author

This could work but I think it's a bit overcomplicated. Besides, I'd rather re-implement the Path classes first with a more structured code.

@kianenigma
Copy link
Member Author

Idea:
We could have two messaging types.

  1. The way it is now: messages will get resolved at the sender ( if required )
  2. Pub/Sub style where Receiver resolves messages based on path (should check wildcard)

This can also be implemented as a high-level functionality in a bootstrap function. we can overrdie sr.bindTransportEvents and add a new .pub .sub method to xyz

@kianenigma
Copy link
Member Author

the title is invalid. it should not be allowed. BUT

using .subscribe() we should be able to listen to sub paths. As an example, listening on / should be invoked on every call.

needs:

  • stronger validation to ensure register(*) is not allowed.
  • listeing on /

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

No branches or pull requests

1 participant