You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current dialplan was not correct and complicated. This rework
simplify it greatly and provide an easy way to do your own routing
I think it will be a nice place to put helpers for
authentifications.
No idea if that will provide any advantages over a flat mapping
of methods / middlewares
issue #78
Current dialplan was not correct and complicated. This rework
simplify it greatly and provide an easy way to do your own routing
I think it will be a nice place to put helpers for
authentifications.
No idea if that will provide any advantages over a flat mapping
of methods / middlewares
issue #78
Current dialplan was not correct and complicated. This rework
simplify it greatly and provide an easy way to do your own routing
I think it will be a nice place to put helpers for
authentifications.
No idea if that will provide any advantages over a flat mapping
of methods / middlewares
issue #78
Currently, if the dialplan falls through, it returns a 501. But that strictly isn't correct.
For example, if the server implements SUBSCRIBE, but its gated behind a particular user, it should return 404 back, for example.
Maybe it even makes sense to just drop that and have a flat mapping of methods to callbacks and leave these kinds of decisions to the library users?
After all, I think a lot of this functionality could be nicely gated behind middleware.
The text was updated successfully, but these errors were encountered: