Openfire - 未使用自定义数据库从数据库更新名册上的组
我在 Openfire 小组中提出了这个问题，但那里似乎很安静。也许 SO 的某个人使用 Xiff/Openfire 并对此有一个线索：
我们在 Openfire 3.6.4 到 Xiff 3.0 beta 上与我们自己的客户端一起使用用户和组的外部数据库。
当用户添加到我们的数据库中时，名册不会更新。我以“User1”身份登录。 “User2”已添加到数据库中的同一共享组中，因此我应该在我的名册中看到他。 User2 可以登录并在其名册上查看 User1，但 User1 的名册尚未更新。即使注销后，User2 仍然不会出现在 User1 的名册上。
显然该组正在被缓存或其他什么。我应该在哪里寻找解决此问题的方法？希夫？开火？我在文档中找到了“cache.name.maxLifetime”属性，但我不确定这是否是我应该用来获取组来更新成员的属性。
I made this question over at the Openfire groups, but it seems to be pretty quiet out there. Maybe someone here at SO works with Xiff/Openfire and has a clue about this:
We are using an external database for users and groups, on Openfire 3.6.4 through Xiff 3.0 beta with our own client.
When a user is added on our database, the roster doesn't get updated. I am logged in as "User1". "User2" is added to the database to the same shared group, so I should see him in my roster. User2 can login and see User1 on his roster, but User1's roster hasn't been updated. Even after log out, User2 still doesn't show up on User1's roster.
Apparently the group is being cached or something. Where should I be looking at for a fix to this problem? Xiff? OpenFire? I found about the property "cache.name.maxLifetime" in the docs, but I'm not sure if this is the property I should be using to get groups to update the members.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果有人来这里寻找这个问题的答案，您可以在这里关注：
未使用自定义数据库从数据库更新名册上的组
Ignite Realtime 论坛上有部分解决方案。
In case anybody gets here looking for an answer to this question, you can follow it here:
Groups not updated on Roster from Database using custom DB
There's a partial solution over there at the Ignite Realtime forums.
更好的方法是使用名册协议（请参阅 RFC 3921，第 7 节）修改名册，也许可以通过为 OpenFire 编写一个组件来实现。这将修改传输中的缓存，并向用户当前登录的客户端发送通知。同样，您的更改也不会被覆盖。
A better approach would be to use roster protocol (see RFC 3921, section 7) to modify the roster, perhaps by writing a component for OpenFire. This will modify the caches in transit, as well as sending notifications to clients that are currently logged in for the user. As well, you won't have issues with your changes getting overwritten.