privilege: store roster cache in database: - rosters are now stored on database and restored on startup. This way, presence map can be restored without the need to wait for all contact to send presence again - roster version are checked, if a new version is received, presence map is updated accordingly - roster are not retrieved if presence are received in a too short delay (see ROSTER_TTL), to avoid using too much resources if a client connect/disconnect a lot The current behaviour works around XEP-0356 limitations. An update of the XEP will be needed to get roster pushes and roster version.

b2149e448465d54e39bb8892ba9ded3313510738 idavoll-0.5.0
e289636ccc4f9e3690879aaf7b9bb5f2674c3fc8 idavoll-0.7.3
560b6cdc50b20d7590a70b0311d4781e3296c589 0.1.0
232002e132dbf9c7563d9f78f4b5e2bcdc2764de 0.1.1
642dffb9d6f1e7b2e7d5e9cb6ba17b6950fdf0bb 0.2.0
0861da6975b57dcaa1c69b2833232fe191346f87 0.3.0