1. 21 May, 2015 1 commit
  2. 03 Jun, 2014 1 commit
  3. 07 Jan, 2014 1 commit
  4. 23 Aug, 2012 2 commits
  5. 20 Aug, 2012 2 commits
  6. 16 Aug, 2012 1 commit
  7. 14 Aug, 2012 1 commit
  8. 01 Aug, 2012 1 commit
  9. 24 Jul, 2012 1 commit
  10. 23 Jul, 2012 1 commit
  11. 13 Jul, 2012 1 commit
  12. 21 Mar, 2012 2 commits
  13. 13 Mar, 2012 1 commit
  14. 12 Mar, 2012 1 commit
    • Julien Muchembled's avatar
      New feature to check that partitions are replicated properly · 04f72a4c
      Julien Muchembled authored
      This includes an API change of Node.isIdentified, which now tells whether
      identification packets have been exchanged or not.
      All handlers must be updated to implement '_acceptIdentification' instead of
      overriding EventHandler.acceptIdentification: this patch only does it for
      StorageOperationHandler
      04f72a4c
  15. 28 Feb, 2012 1 commit
  16. 17 Jan, 2012 1 commit
  17. 06 Jan, 2012 1 commit
  18. 05 Jan, 2012 1 commit
  19. 26 Oct, 2011 2 commits
  20. 05 Sep, 2011 1 commit
  21. 02 May, 2011 1 commit
  22. 27 Apr, 2011 1 commit
    • Julien Muchembled's avatar
      connection: make close always call handler (connectionClosed or connectionFailed) · 4b6c1387
      Julien Muchembled authored
      Main reason is that it's difficult to know in advance which side really closes
      the connection. Network events can be chaotic and this could lead to many race
      conditions.
      Thus, handler can be used to update any database that is somewhat redundant
      to the connection status, i.e. node status usually. Safely and less duplicated
      code.
      
      This change is motivated by recurrent random failures during election.
      An example of race condition was that 2 fully connected master could close the
      extra connection (the primary -> secondary one) at the same time.
      
      In order to stabilize lower-level code and start with reliable election process,
      code has also been simplified to not care about node states. All connections
      without exception are closed at the end of the election and states are then
      updated 1 by 1 by identification handler.
      Note that during election, there may be 2 connection per node, which makes
      difficult to update node states by connectionFailed/connectionClosed events.
      
      timeoutExpired & peerBroken are dropped as they are unused for the moment.
      A new API should be designed so that connectionClosed know the reason of the
      close.
      BROKEN state becomes unused.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2732 71dcc9de-d417-0410-9af5-da40c76e7ee4
      4b6c1387
  23. 25 Feb, 2011 1 commit
    • Olivier Cros's avatar
      Implementing ipv6 on neo · 0cdbf0ea
      Olivier Cros authored
      In order to synchronise neo with slapos, it has to work perfectly with ipv4
      and ipv6. This allows to integrate neo in erp5 and to prepare different buildout
      installations of neo.
      The protocol and connectors are no more generic but can now support IPv4 and
      IPv6 connections. We adopted a specific way of development which allow to
      easily add new protocols in the future.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2654 71dcc9de-d417-0410-9af5-da40c76e7ee4
      0cdbf0ea
  24. 17 Jan, 2011 1 commit
  25. 05 Nov, 2010 1 commit
  26. 01 Nov, 2010 2 commits
  27. 16 Sep, 2010 1 commit
  28. 30 Apr, 2010 1 commit
  29. 16 Mar, 2010 3 commits
  30. 08 Mar, 2010 1 commit
  31. 01 Mar, 2010 1 commit
  32. 08 Feb, 2010 1 commit
  33. 01 Feb, 2010 1 commit