1. 19 Sep, 2007 3 commits
    • guus's avatar
      User now implements the Result interface, to make User objects suited for... · a7b4aee9
      guus authored
      User now implements the Result interface, to make User objects suited for Result Set Management. Any user listing (the search plugin, for example) will benefit from this.
      
      git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/branches/rsm@9167 b35dd754-fafc-0310-a699-88a17e54d16e
      a7b4aee9
    • guus's avatar
      Currently, there's an interface defining a DiscoItem object. There's no... · 93f63ed9
      guus authored
      Currently, there's an interface defining a DiscoItem object. There's no implementation of it, other than in-line implementations in methods (the same goes for the sub-interface, DiscoServerItem). Where manipulations of DiscoItem objects are done, Dom4J Element instances are used instead. The DiscoItem interface has been replaced by an implementation of that interface (again, same goes for the sub-interface, which is now a subclass). As I assumed there would not be other implementations of the same interface (which would give you 'another kind' of DiscoItem objects, but what's the point?), I removed the interface completely.
      
      As a result of the changed representation, the DiscoItemsProvider interface now declares a method that returns an Iterator of DiscoItem objects, instead of Elements. This caused changes in a number of classes.
      
      Result Set Management functionality has been added, which causes all disco#items request to be result set managable (this is, for instance, useful for large listings or MUC rooms).
      
      git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/branches/rsm@9166 b35dd754-fafc-0310-a699-88a17e54d16e
      93f63ed9
    • guus's avatar
      A new package that defines an interface definition for a 'manageable result'... · 4bc5ef9d
      guus authored
      A new package that defines an interface definition for a 'manageable result' and an interface + default implementation for managing results. The set-up is as such, that it would be easy to implement another manager that does not need the entire resultset to base its calculations on. That can cause significant performance gains for result sets that are resource expensive to acquire or maintain in memory.
      
      git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/branches/rsm@9165 b35dd754-fafc-0310-a699-88a17e54d16e
      4bc5ef9d
  2. 18 Sep, 2007 2 commits
  3. 07 Sep, 2007 1 commit
  4. 15 Aug, 2007 1 commit
  5. 07 Aug, 2007 3 commits
  6. 02 Aug, 2007 1 commit
  7. 26 Jul, 2007 1 commit
  8. 25 Jul, 2007 1 commit
  9. 22 Jul, 2007 5 commits
  10. 20 Jul, 2007 2 commits
  11. 19 Jul, 2007 1 commit
  12. 17 Jul, 2007 2 commits
  13. 16 Jul, 2007 1 commit
  14. 14 Jul, 2007 3 commits
  15. 11 Jul, 2007 1 commit
  16. 08 Jul, 2007 3 commits
  17. 07 Jul, 2007 1 commit
  18. 06 Jul, 2007 2 commits
  19. 05 Jul, 2007 6 commits