Custom Query (257 matches)
Results (34 - 36 of 257)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #264 | ph3-der-loewe | fixed | There should be a protocol ID range for user defined usage | |
| Description |
There should be a range for User defined protocols. Those IDs should be allowed to be passed over the wire if client and server agree on the meaning before. This can for example be done using the CAPS command if the RoarAudio Protocol is used. See Specs/ProtocolValues for technical details, use this ticket for discussion. |
|||
| #265 | ph3-der-loewe | fixed | There should be a protocol ID range for dynamic usage | |
| Description |
There should be a range of protocol IDs which can be used for dynamic services. This includes running stuff like gimmiks and games no protocol ID is assigned to. In contrast to IDs in the user range (see #264) they MUST NOT be send over the wire or stored on disk. They are only valid within a single application at a single runtime. See Specs/ProtocolValues for technical details, use this ticket for discussion. |
|||
| #275 | ph3-der-loewe | ph3-der-loewe | fixed | roard should auto load plugins for missing protocols |
| Description |
roard should automatically load plugins for protocols used but not supported internally or no other plugins already provides. To do this it should try to load the plugin "protocol-$PROTONAME", with $PROTONAME the symbolic name of the protocol. |
|||
