1. 08 Nov, 2016 1 commit
  2. 05 Nov, 2016 1 commit
  3. 04 Nov, 2016 1 commit
    • Michael Klein's avatar
      OF-1211 - Fix description of Broadcast disabling option in Client (#663) · 57e24df5
      Michael Klein authored
      * OF-1211 - Fix description of Broadcast disabling option in Client
      Control plugin
      
      * OF-1211 - Fix description of Broadcast disabling option in Client
      
      * OF-1211 - Fix description of Broadcast disabling option in Client
      
      * OF-1211 - Fix description of Broadcast disabling option in Client
      
      * Revert "OF-1211 - Fix description of Broadcast disabling option in Client"
      
      This reverts commit fa12c8169b556c1d4d157a57609648e69637499a.
      
      * Revert "OF-1211 - Fix description of Broadcast disabling option in Client"
      
      This reverts commit 84a52e90e794eff62fc13a0330544fe16c850575.
      
      * OF-1211 - Fix description of Broadcast disabling option in Client
      
      * OF-1211 - Fix description of Broadcast disabling option in Client
      57e24df5
  4. 01 Nov, 2016 2 commits
  5. 28 Oct, 2016 1 commit
  6. 23 Oct, 2016 1 commit
  7. 21 Oct, 2016 1 commit
  8. 20 Oct, 2016 1 commit
  9. 18 Oct, 2016 1 commit
    • Gugli's avatar
      OF-1206: PrivacyLists on first run (#656) · 0d3b3a38
      Gugli authored
      * PrivacyLists on first run
      There are 2 instances of PrivacyListProvider (one in PrivacyListManager and the other in IQPrivacyHandler)
      
      The issue was : both instances have separate privacyListCount variables, which are filled during PrivacyListProvider constructor (== server startup).
      Thus, if at server startup the privacyListCount is 0, and one of the instances adds a PrivacyList, the other will never be informed and discard all changes and reads.
      
      Fix : turn PrivacyListProvider into a singleton.
      
      * PrivacyLists on first run
      There are 2 instances of PrivacyListProvider (one in PrivacyListManager and the other in IQPrivacyHandler)
      
      The issue was : both instances have separate privacyListCount variables, which are filled during PrivacyListProvider constructor (== server startup).
      Thus, if at server startup the privacyListCount is 0, and one of the instances adds a PrivacyList, the other will never be informed and discard all changes and reads.
      
      Fix : turn PrivacyListProvider into a singleton.
      0d3b3a38
  10. 11 Oct, 2016 2 commits
  11. 07 Oct, 2016 2 commits
  12. 03 Oct, 2016 13 commits
  13. 30 Sep, 2016 2 commits
  14. 28 Sep, 2016 1 commit
  15. 27 Sep, 2016 3 commits
  16. 26 Sep, 2016 3 commits
  17. 06 Sep, 2016 1 commit
  18. 25 Aug, 2016 1 commit
  19. 22 Aug, 2016 1 commit
  20. 17 Aug, 2016 1 commit