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

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

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

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

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

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

See IteratorTests.checkSimpleIteration from ZODB tests.

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

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

As done in the FileStorage and expected by ZODB tests (see checkClose).

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

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

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

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

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

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

General purpose packet to log a message on a remote peer.

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

- Rename IdleEvent to IdleTimeout from event.py to connection.py
- Move connection-related logic in Connection itself and keep only
time-related logic in IdleTimeout
- Clarify differences between hard and soft timeouts.
- Remove (unused) 'additional_timeout' from ask()
- Remove (now useless) event_dict attribute from Connection.
- Remove external ping support, as the answer can not be handled at
application level.
- Expectation after a new incoming connection moved from Handler to
Connection.
- Fix (and clean) related tests.

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

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

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

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

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

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

It is possible to have a transactional undo of object creation without
having the object in cache.
For some reason, it happens in 6.9GB FileStorage import.

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

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

This makes Packet.__repr__ mad when used to trace what the test is doing.

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

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

Remove MT* tests as then are just copy/paste of non-MT tests.

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

Merge both into 'connector' only to simplify API.

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

Just to avoid complains from pylint :)

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

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