Adam Cameron. wrote:
Like I said: you're confused: you are misunderstanding the meaning of "public" in the context of CFC method access levels. "Public" does NOT mean "public access".
Read the docs I pointed you at.
I read the your reference. I was already familiar with the stuff. You are the one who seems to be confused, mate. It requires a little leap in interpretation.
The original poster said, "CF10 websocket p2p can invoke any public functions in any CFC from JavaScript". So he uses "public" as an adjective. You yourself wrote, "PUBLIC methods should not be web-accessible.". So, you, too, use "public" as an adjective.
The context is implicitly clear. Public, not as in general public, but public, as opposed to private, package, etc. Incidentally, whereas you, two, talk about functions and methods, I talk about interfaces. That is in keeping with the theme I focussed upon, design.