1. 10 Oct, 2018 1 commit
  2. 18 Sep, 2018 1 commit
  3. 27 Aug, 2018 2 commits
  4. 22 Aug, 2018 1 commit
  5. 16 Aug, 2018 1 commit
  6. 11 Jun, 2018 2 commits
  7. 29 May, 2018 1 commit
  8. 24 Apr, 2018 2 commits
  9. 20 Apr, 2018 1 commit
  10. 29 Mar, 2018 3 commits
  11. 23 Jan, 2018 1 commit
  12. 09 Jan, 2017 1 commit
  13. 30 Aug, 2016 2 commits
  14. 23 Jun, 2016 2 commits
    • Ard Schrijvers's avatar
      447c8d3c
    • Ard Schrijvers's avatar
      HIPPLUG-1308 make sure every worker has its own urlset · 031750fa
      Ard Schrijvers authored
      The Urlset object should have to think about synchronization. It is the code
      that uses the Urlset that shouldn't expect the Urlset to be thread-safe (just
      like a HashSet isn't thread-safe. It make much more sense to not give all the
      workers a reference to the same urlset object but all have their own
      
      A seperate note is that I really think the worker should not extend from
      Thread and a lot of the complex logic can be replaced by a simple executer service
      031750fa
  15. 23 May, 2016 1 commit
  16. 25 Feb, 2016 1 commit
  17. 30 Jan, 2016 3 commits
  18. 26 Jan, 2016 5 commits
  19. 08 Jan, 2016 1 commit
  20. 06 Nov, 2015 1 commit
  21. 13 Oct, 2015 4 commits
  22. 11 Aug, 2015 2 commits
  23. 13 Jul, 2015 1 commit