Changeset 548 in code for trunk/doc/ext
- Timestamp:
- May 29, 2021, 11:18:06 AM (4 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/ext/bouncer-networks.md
r537 r548 43 43 a new `BOUNCER` command. 44 44 45 The `soju.im/bouncer-networks` capability MUST be nego ciated. This allows the45 The `soju.im/bouncer-networks` capability MUST be negotiated. This allows the 46 46 server and client to behave differently when the client is aware of the bouncer 47 47 networks. 48 48 49 The `soju.im/bouncer-networks-notify` capability MAY be nego ciated. This allows49 The `soju.im/bouncer-networks-notify` capability MAY be negotiated. This allows 50 50 the client to signal that it is capable of receiving and correctly processing 51 51 bouncer network notifications. … … 136 136 ### Network notifications 137 137 138 If the client has nego ciated the `soju.im/bouncer-networks-notify` capability,138 If the client has negotiated the `soju.im/bouncer-networks-notify` capability, 139 139 the server MUST send an initial batch of `BOUNCER NETWORK` messages with the 140 140 current list of network, and MUST send notification messages whenever a network 141 141 is added, updated or removed. 142 142 143 If the client has not nego ciated the `soju.im/bouncer-networks-notify`143 If the client has not negotiated the `soju.im/bouncer-networks-notify` 144 144 capability, the server MUST NOT send implicit `BOUNCER NETWORK` messages. 145 145
Note:
See TracChangeset
for help on using the changeset viewer.