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

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

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

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

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

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

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

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

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

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

There is nothing to clean on the master side when a client abort a
transaction.

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

Master transactions objects are instanciated during the finish phase only,
which means that any transaction known by the master is being committed.

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

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

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

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

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

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

FileStorage.copyTransactionsFrom doesn't have a verbose parameter in its
latest version.

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

Avoid switching to an unexpected interpreter after forking.

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

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

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

This has been deprecated at least in Zope 2.8.8, maybe earlier.

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

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

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

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

Also, reverts r2197, as it is unclear what bug it was trying to fix, and it
doens't seem required (there is no call to Replicator.act() outside of
doOperation).

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

This causes garbage collection problems, as BaseConnection instances also
hold a reference to HandlerSwitcher instance. It is unclear why it fails,
as microbenchs show this should not be a problem for gc.
Also, move loggers out of HandlerSwitcher.setHandler to avoid passing a
connection parameter just for them.

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

It is more efficient to provide a boundary value than a row count range.
This fixes replication on partitions with a large number of objects, revisions
or transactions: query time is now constant where it used to increase, causing
timeout problems when query duration exceeded ping time + ping timeout (11s
currently).

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

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

Previous name was too close to the regular-user SQL connection getter.
Also, prevent subclasses from calling it.

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

This made it impossible to detect when a storage didn't contain an object.

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

It is not possible to move them out of container loop, as tid is a loop
variable.

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

Also, stop using a dict in an inefficient way, and replace it by a set.

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

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

Also, factorises packet creation.

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

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

onConnectionClosed is already called inside Connection.close() when peer
is identified (via setOnClose). Calling it here would trigger an exception
as it verifies that _connection is set before un-setting it.
As a replacement, verify that _connection is not set when
Connection.close() returns (so onConnectionClosed was actually called).

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

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

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

It is possible for rid not to be in partition_dict or new_partition_dict,
as this method is called from a master notification (partition changed),
which might happen outside of any replication (so when both dicts are
empty).

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