1. 19 Sep, 2007 3 commits
    • guus's avatar
      User now implements the Result interface, to make User objects suited for... · d903eb63
      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@9167 b35dd754-fafc-0310-a699-88a17e54d16e
      d903eb63
    • guus's avatar
      Currently, there's an interface defining a DiscoItem object. There's no... · 48ba7b30
      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@9166 b35dd754-fafc-0310-a699-88a17e54d16e
      48ba7b30
    • guus's avatar
      A new package that defines an interface definition for a 'manageable result'... · 03efc228
      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@9165 b35dd754-fafc-0310-a699-88a17e54d16e
      03efc228
  2. 18 Sep, 2007 4 commits
  3. 17 Sep, 2007 2 commits
  4. 13 Sep, 2007 4 commits
  5. 07 Sep, 2007 2 commits
  6. 05 Sep, 2007 4 commits
  7. 28 Aug, 2007 1 commit
  8. 21 Aug, 2007 2 commits
  9. 20 Aug, 2007 1 commit
  10. 19 Aug, 2007 3 commits
  11. 17 Aug, 2007 1 commit
  12. 15 Aug, 2007 4 commits
  13. 10 Aug, 2007 6 commits
  14. 09 Aug, 2007 3 commits