irn-chanlist-delta
FORMAT
({ "irn-chanlist-delta", (int), // ttl (string), // srcrouter 0, (string), // dstrouter 0, (int), // chanlistid (mapping) // data })
The data mapping looks like this:
([ "channels" : (mapping) // channel list "listening" : (mapping) // listener list ])
The channel list mapping has channel names as keys, and arrays with the chanlist data as values. The chanlist data array looks like this:
({ (int), // channel type (string), // owning mud (array) // ban/allow list })
The listeners mapping contains channel names as keys and arrays with listening muds as values.
Notes:
- This packet is directly based on the internal data format of the DS based routers, it should be considered for change in a next irn version.
- A mud can decide to only sent the channels or listening part of the data mapping, but it should make sure that when a new channel is added, a channels mapping is sent first. Routers may (and likely will) ignore listening updates for channels they do not know about.
- There is no good reason for synchronizing listeners between routers, this part of the spec is now ignored by all routers on the lpmuds.net i3 network, and the listeners mapping is simply ignored if received.