This API method seems used only in ZODB tests framework.

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

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

See RevisionTests.checkLoadBeforeCreation test case.

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

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

This allow raise KeyError even for getSerial().

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

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

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

KeyError must be raised if the history is empty, see
HistoryTests.checkSimpleHistory test case.

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

- Rename length 'parameter' to 'size'
- Define None as default version.

See HistoryTests.checkSimpleHistory.

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

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

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

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

This method is the symetric of close() on Storage (see previous commit) and
is required for some ZODB tests. Support read_only attribute.

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

Behaviour is not defined for NEO but shutting down the client side seems
really bad (close is aliased to __del__).
Move no-op methods (close & cleanup) at file end, with not implemented ones.

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

See HistoryTests.checkSimpleHistory.

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

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

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

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

Storage.store calls can be pipelined when implementation can take advantage of
it (as Zeo does). This allows reducing the impact of (network-induced, mainly)
latency by sending all objects to storages without waiting for storage answer.

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

Those "properties" were put in _threads_dict (cf __setattr__), but only for
the thread who instantiates ThreadContext (until next "clear" call from/for
that thread, where they are not inserted in cleared version).

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

This causes isolation problems in tests (and was detected because of this)
but would have also caused problem if multiple Storage (and hence App class)
instances were used in a single process.

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

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

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

Reorganize unimplemented methods, gather all at end of file.

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

If ZODBTests is imported at module level, TestLoader handle it and find
dupliucates test cases.

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

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

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

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

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

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

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

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

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

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

It is important that unregistering a response from dispatcher and putting
it in its queue are atomic at dispatcher level to support askStoreObject
pipelining.

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

This fixes problems uncovered by current work on askStoreObject pipelining.

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

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

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

This ensure the cluster is stop and will not alter next rounds.
Use -1 to indicate a failure instead of 0.

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

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