stackd/SabreDAV — comment on commit 543a3d9f54c9d1b3d89c6276984e1cc9b0c3c805
File:  line 0
By evert:

I just wanted to say.. the way you're doing this does not make a lot of sense.. I don't mind, but maybe you find this helpful.

The reason I namespace all my code with Sabre_, is so there's very little chance of collisions with other code. This is pretty much how any PHP library or framework does it. So by using Sabre_DAV_RESTfs as your namespace, you're defeating the purpose.

_and_ the added annoyance is that now you have your own module in a sabredav fork. If you would just see SabreDAV as an important library, you only have to import the git submodule from your main project. Your own RESTfs gets its own prefix (Sausman_ ?). If you look at other people implementing SabreDAV (Horde or Owncloud) you'll notice that that's also how they do it.

This is just a very odd way to do things, and I keep noticing because these commits end up in the SabreDAV network graph, while they are completely unrelated to the project :)