Clarify that people must own the namespace to use it
This commit is contained in:
parent
8fd5b15594
commit
51698a5dd5
2 changed files with 4 additions and 2 deletions
|
@ -1330,7 +1330,8 @@ namespaced for each application and reduces the risk of clashes.
|
|||
Events are not limited to the types defined in this specification. New or custom
|
||||
event types can be created on a whim using the Java package naming convention.
|
||||
For example, a ``com.example.game.score`` event can be sent by clients and other
|
||||
clients would receive it through Matrix.
|
||||
clients would receive it through Matrix, assuming the client has access to the
|
||||
``com.example`` namespace.
|
||||
|
||||
Note that the structure of these events may be different than those in the
|
||||
server-server API.
|
||||
|
|
|
@ -352,7 +352,8 @@ from the other servers participating in a room.
|
|||
Events are not limited to the types defined in this specification. New or custom
|
||||
event types can be created on a whim using the Java package naming convention.
|
||||
For example, a ``com.example.game.score`` event can be sent by clients and other
|
||||
clients would receive it through Matrix.
|
||||
clients would receive it through Matrix, assuming the client has access to the
|
||||
``com.example`` namespace.
|
||||
|
||||
Room Aliases
|
||||
++++++++++++
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue