...
- Just prepend namespace to topic names, inheritance will be tricky and not so intuitive. even at storage layer, instead of creating a hierarchy of directories to represent namespaces.
- Will not enable encrypting namespaces with different keys
- .
- Inheritance will be tricky and not so intuitive.
- Manage namespaces separately, this .
- This will still have the issue of topic name collisions even if they belong to separate namespaces.
- Modify request/ response formats to take namespace specifically.
- Solves the issue of delimiting string required in proposed approach. However, will require
- lots of API and protocol changes.
- Add namespace to session object.
- Will avoid each request and response to have namespace with topic name, however this probably is violating separation of concerns.
- To have delimiter char configurable.
- Will add yet another config without a clear gain.