Master nodes don't exchange node informations during election, this packet
handler is not implemented and so unexpected.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1882 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1881 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1880 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1879 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1878 71dcc9de-d417-0410-9af5-da40c76e7ee4

This fixes the inability to undo T-1 after undoing T.
For reference, this is what is done in RelStorage. It is not as restrictive
as FileStorage, but implementing the same support would/will take more
time.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1877 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1876 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1875 71dcc9de-d417-0410-9af5-da40c76e7ee4

The main purpose is to apply and handler after all pending requests are
satisfied and allow process answer packets of current state out of order.
This fix a bug that appears when a storage tries to get a lock on an object that
is already held by a previous transaction. Is this case the store is delayed
causing the answer packet be sent out of order (packet sequence breakage), so
unexpected from client's point of view.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1874 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1873 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1872 71dcc9de-d417-0410-9af5-da40c76e7ee4

Strangely, nothing in FileStorage forces a new transaction to start with a
TID higher than previous transaction. Supporting this is required for a
ZODB test to pass, so just do that - with a warning.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1871 71dcc9de-d417-0410-9af5-da40c76e7ee4

If EPOLLERR or EPOLLHUP is asserted, the event will be appended to
readable_fd_list, so it is useless to test their value in the second
test too.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1870 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1869 71dcc9de-d417-0410-9af5-da40c76e7ee4

This should improve scalability when the number of non-client nodes grows.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1868 71dcc9de-d417-0410-9af5-da40c76e7ee4

The __undoLog() method is used by undoLog() and transactionLog() with
different parameters. When a recursive call is made, keep initial arguments
instead of always call as if it was undoLog().

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1867 71dcc9de-d417-0410-9af5-da40c76e7ee4

When called, queued events were using the last peer message id instead of
having the good one on their connection when recalled, so answers made from
queued events was using the wrong message id.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1866 71dcc9de-d417-0410-9af5-da40c76e7ee4

This is not fixed, IdleEvent is not associated to the packet that create it.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1865 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1864 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1863 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1862 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1861 71dcc9de-d417-0410-9af5-da40c76e7ee4

This fixes undo support in client without changing the way replication is
implemented.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1860 71dcc9de-d417-0410-9af5-da40c76e7ee4

Store does not handle conflicts (for reliability, it can only be done once
all store responses are received), so this parameter must go away.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1859 71dcc9de-d417-0410-9af5-da40c76e7ee4

Aborting might happen even before vote is called, wot there might be
pending store responses. Wait for them without doing conflict handling.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1858 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1857 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1856 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1855 71dcc9de-d417-0410-9af5-da40c76e7ee4

If anything went wrong, an exception must be raised before this point.
And if everything has been fine, oid_list and data_dict.keys() are the
same.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1854 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1853 71dcc9de-d417-0410-9af5-da40c76e7ee4

Reduces the amount of duplicated (or deductible) information in packet
generators and parsers.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1852 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1851 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1850 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1849 71dcc9de-d417-0410-9af5-da40c76e7ee4

Computation of next TID is now part of master's transaction manager.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1848 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1847 71dcc9de-d417-0410-9af5-da40c76e7ee4

- Allow a fine-grained test suite.
- Avoid shadow internal method definitions.
- Remove some meaningless checks

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1846 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1845 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1844 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1843 71dcc9de-d417-0410-9af5-da40c76e7ee4