1. 09 Feb, 2012 1 commit
  2. 07 Feb, 2012 1 commit
  3. 03 Feb, 2012 1 commit
  4. 31 Jan, 2012 1 commit
  5. 25 Jan, 2012 2 commits
  6. 24 Jan, 2012 1 commit
  7. 20 Jan, 2012 1 commit
  8. 19 Jan, 2012 2 commits
  9. 06 Jan, 2012 4 commits
  10. 02 Jan, 2012 1 commit
  11. 01 Jan, 2012 5 commits
  12. 20 Dec, 2011 1 commit
  13. 15 Dec, 2011 2 commits
  14. 10 Dec, 2011 1 commit
  15. 01 Dec, 2011 1 commit
  16. 30 Nov, 2011 1 commit
  17. 24 Nov, 2011 1 commit
  18. 17 Nov, 2011 1 commit
  19. 22 Oct, 2011 1 commit
  20. 17 Oct, 2011 2 commits
  21. 16 Oct, 2011 5 commits
  22. 02 Oct, 2011 1 commit
  23. 01 Oct, 2011 1 commit
  24. 25 Sep, 2011 1 commit
  25. 24 Sep, 2011 1 commit
    • guus's avatar
      OF-443: No longer use the dialback namespace definition as a trigger to start... · 55d8c08f
      guus authored
      OF-443: No longer use the dialback namespace definition as a trigger to start dialback (but use the db:verify / db:result elements instead). When the reported version of the stream is absent (prevents compatibility issues with openfire before version 3.7.1) or smaller than one, nothing should be sent on the stream before a db:verify / db:result stanza is sent (no stream features, for example). This mimics old behaviour. This way, dialback appears to be triggered by the namespace definition in the stream (even though in actuality it's triggered by a child element) which makes things backwards compatible.
      
      git-svn-id: http://svn.igniterealtime.org/svn/repos/openfire/trunk@12837 b35dd754-fafc-0310-a699-88a17e54d16e
      55d8c08f