- 22 Mar, 2018 1 commit
-
-
Guus der Kinderen authored
Openfire supports XEP-0049, Private XML Storage. However, Openfire can also be used for XEP-0223: Persistent Storage of Private Data via PubSub. When a user previously used more than one client, where each client would use a different XEP to store private data, the private data that was stored by one client would not be shared with the other client. This is undesirable, as such data typically includes data that benefits every client used by the user. In this commit, all data that is stored in the Private XML Storage database table will be migrated to PEP. After a successful migration, the old database table is deleted. Openfire continues to offer XEP-0049: Private XML Storage functionality. However, whenever data is obtained or modified through methods defined in that XEP, the PEP data is modified.
-
- 14 Nov, 2017 2 commits
- 26 Apr, 2017 1 commit
-
-
Guus der Kinderen authored
Javadoc comment are dangling if they don't belong to any class, method or field. For example a Javadoc comment in between method declarations that have their own javadoc comments. These generate needless warnings, which are in most instances easily solved. By far most problems occur in the license block that's in most files.
-
- 24 Sep, 2014 1 commit
-
-
Roman S. authored
-
- 17 Nov, 2012 1 commit
-
-
Robin Collier authored
git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/trunk@13356 b35dd754-fafc-0310-a699-88a17e54d16e
-
- 06 Jan, 2010 1 commit
-
-
guus authored
Partial rewrite of the PEP implementation. A cache is used that's regularly cleaned, which should improve concurrency and reduce the memory footprint (OF-82). git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/trunk@11498 b35dd754-fafc-0310-a699-88a17e54d16e
-