An error occurred fetching the project authors.
  1. 17 Jan, 2011 1 commit
  2. 23 Feb, 2010 1 commit
  3. 10 Feb, 2010 1 commit
  4. 01 Feb, 2010 3 commits
    • Vincent Pelletier's avatar
      Exit election as soon as primary master is known. · 81ee387a
      Vincent Pelletier authored
      It has no meaning to stay in election state when the primary master is
      known. Also, it causes problems as the elected primary master will soon
      start sending packets we don't expect while election is running.
      
      handler/election.py:
      - Receiving announcePrimary is enough to exit election immediately, so
        reach election end condition (both sets must be empty)
      - Receiving answerPrimary with a known primary is enough to exit election
        immediately (don't attempt to connect to to primary master).
      app.py:
      - Apply PrimaryHandler while iterating over connections when the primary
        master connection is found, rather than once all other connections are
        closed.
      - If no primary master connection was found, start establishing one.
      handlers/secondary.py:
      - Handle connectionCompleted event as we might only reach primary master
        once with this handler if connection was not established during election.
      - Likewise, handle connectionFailed event, and treat it as a primary
        failure.
      - Stop ignoring answerPrimary packets, instead check that advertised
        primary master is the expected one and request node identification.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@1583 71dcc9de-d417-0410-9af5-da40c76e7ee4
      81ee387a
    • Grégory Wisniewski's avatar
      Update copyright. · a88d3eb2
      Grégory Wisniewski authored
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@1576 71dcc9de-d417-0410-9af5-da40c76e7ee4
      a88d3eb2
    • Grégory Wisniewski's avatar
      Remove 'packet' parameter of handler's methods. · 37c75a72
      Grégory Wisniewski authored
      Almost any use of packet was to retreive the msg_id of the request and pass it to answer().
      In storage's replicator, critical TIDs are indexed with UUID instead of remote connection ID (full replicator review required).
      In admin node, expected answers are still queued with the msg_id but it seems useless as no concurrent queries should happen.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@1569 71dcc9de-d417-0410-9af5-da40c76e7ee4
      37c75a72
  5. 28 Jan, 2010 1 commit
  6. 26 Jan, 2010 1 commit
  7. 20 Jan, 2010 1 commit
  8. 13 Jan, 2010 1 commit
  9. 07 Oct, 2009 1 commit
  10. 05 Oct, 2009 1 commit
  11. 01 Oct, 2009 2 commits
  12. 30 Sep, 2009 2 commits
  13. 29 Sep, 2009 1 commit
  14. 04 Aug, 2009 1 commit
  15. 03 Aug, 2009 2 commits
  16. 31 Jul, 2009 1 commit
  17. 30 Jul, 2009 1 commit
  18. 29 Jul, 2009 2 commits
  19. 28 Jul, 2009 1 commit
  20. 17 Jul, 2009 2 commits
  21. 10 Jul, 2009 1 commit
  22. 08 Jul, 2009 2 commits
  23. 03 Jul, 2009 1 commit
  24. 01 Jul, 2009 1 commit
  25. 26 Jun, 2009 1 commit
  26. 24 Jun, 2009 3 commits
  27. 22 Jun, 2009 1 commit
  28. 21 May, 2009 2 commits
  29. 19 May, 2009 1 commit