4 Events are currently designed for useage with pep notifications, but |
4 Events are currently designed for useage with pep notifications, but |
5 potentially could be used with any notification system, eg a module, that adds |
5 potentially could be used with any notification system, eg a module, that adds |
6 currently playing song to your status. |
6 currently playing song to your status. |
7 |
7 |
8 Every module pair (eg pep_tune and tune) use a pair of hooks. One for incoming |
8 Every module pair (eg pep_tune and tune) use a pair of hooks. One for incoming |
9 notifications ('*-in') and one for the cases, when server needs to be notified |
9 notifications ('\*-in') and one for the cases, when server needs to be notified |
10 about user state change ('*-out'). Note, that '*-out' causes server |
10 about user state change ('\*-out'). Note, that '\*-out' causes server |
11 notification, not vice versa. In general, these hooks have the same set of fields, |
11 notification, not vice versa. In general, these hooks have the same set of fields, |
12 except that incoming events also have 'from' field, that is mandatory. |
12 except that incoming events also have 'from' field, that is mandatory. |
13 |
13 |
14 For more clear description of fields and what can be put in there, refer to |
14 For more clear description of fields and what can be put in there, refer to |
15 corresponding XEPs. |
15 corresponding XEPs. |