NSNotification - Missing a rationale for the reverse DNS identifier

Question

NSNotification - Missing a rationale for the reverse DNS identifier

Closed this issue 10 years ago · 3 comments

When you define you own NSNotification you should define your notification's name as a string constant. [...] The value of the constant should be a reverse DNS identifier.

What is the rationale on this? Why isn't the three-letter prefix enough?

Answer 1 · 2014-07-14T14:40:24.000Z

I'll add a "me too" here. The three letter prefix is sufficient. If I saw the reverse DNS identifier I'd assume the value was being used outside of the normal scope of NSNotification.

Answer 2 · 2014-07-17T19:44:43.000Z

Same here, think prefix is enough.

Answer 3 · 2014-07-24T11:20:36.000Z

Thank you for bright this to our attentions and sorry for the delay in the response.

I believe that you all are right and the prefix should be enough. I'll update the book according.