Q:

Should I create a own .h file for my protocol and are there naming conventions for them?

When I create a protocol, I was used to put it right into the .h from a class that this protocol belongs to. But what when I want a pretty "general" protocol that a lot of classes might use? Would I make a .h file for this protocol only? And if so, are there special naming conventions to distinguish it from a class header file?

A:

I think whatever is the clearest, most obvious way of doing it is the "right" way. In the case you describe having the protocol in its own header file probably does make sense.
There's no generally accepted naming convention for protocols so, again, call it something that makes sense.

