I know the recommendation is to add them to prevent conflicts but We've been using crossbar going on 2 years now and we haven't been using reverse domains up to this point, our URIs look like this 'auth.oktai.password.verify' it hasn't been a problem yet.
we're putting together a technical doc on integrating into our apps via crossbar and revisiting the recommendation, on one hand it makes sense to require 3rd parties integrating into our app to include their domain e.g. 'com.example.password.verify' but doing so means we should to fully adopt the convention and refactor all of our URIs so ours would become 'com.ourdomain.password.verify'
I'm hoping someone can offer advice for our against to help us determine if it's really important or not.
--
You received this message because you are subscribed to the Google Groups "Crossbar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crossbario+...@googlegroups.com.
To post to this group, send email to cross...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/crossbario/a9be25f3-6fc3-41be-a207-03da17ad48fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.