Ticket #3190 (new enhancement)

Opened 17 months ago

Last modified 9 months ago

Roster cache in database

Reported by: Liorithiel Owned by: asterix
Priority: normal Milestone:
Component: history Version:
Severity: minor Keywords: logs roster database
Cc: OS: All

Description

logs.db could have a cache of user roster, as an another table. Purpose: show roster even when offline, a backup of roster (in case of server being down), play with roster from outside gajim (f.e. external scripts to parse logs, like beagle).

It would store only jid/nickname mapping or full vcards.

Attachments

Change History

in reply to: ↑ description   Changed 9 months ago by anonymous

  • priority changed from low to normal
  • os set to All

Replying to Liorithiel:

logs.db could have a cache of user roster, as an another table. Purpose: show roster even when offline, a backup of roster (in case of server being down), play with roster from outside gajim (f.e. external scripts to parse logs, like beagle). It would store only jid/nickname mapping or full vcards.

This would be *realy* nice to see in gajim. Are there any activities about it? Local roster is a must have, I think.

  Changed 9 months ago by asterix

yep, would be nice, but no activity about that for the moment

Add/Change #3190 (Roster cache in database)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.