Page History

...

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