Ceph

Markus Elfring wrote:

This issue corresponds to my previous feature request.

I suggest to add at least one namespace to the source files of your class library.

Examples:
source:src/include/ClassLibrary.h@e49a67302d4e59a47b3722a6daa4aa7de77fb772#L16
source:src/include/Context.h@83203b5ed4afd87f1046e0e5f00f95cac82c6af4#L17

Would you like to reduce the probability for name clashes?

Namespaces would be great. I've added a 'ceph' namespace to a few of the headers in include/, but so far that's it.

The main issue is I'm not certain how best to organize the namespace. One 'ceph' namespace for everthing? Nested namespaces, so that ceph::mds::(C)Inode is distinct from mds::uclient::Inode? etc. Suggestions/patches welcome!

Can a bit of C++ namespaces advice help to clarify your software design?

Markus Elfring wrote:

Can a bit of C++ namespaces advice help to clarify your software design?

Okay, this makes me think a single 'ceph' namespace is just fine.