On Tue, Aug 28, 2012 at 06:31:05PM +0200, Vincent Pelletier wrote:
On Tue, 28 Aug 2012 16:31:20 +0200,
Martijn Pieters m...@zopatista.com wrote :
Anything else different? Did you make any performance comparisons
between RelStorage and NEO?
I believe the main difference compared to all
On Wed, Aug 29, 2012 at 2:29 AM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Aug 28, 2012 at 06:31:05PM +0200, Vincent Pelletier wrote:
On Tue, 28 Aug 2012 16:31:20 +0200,
Martijn Pieters m...@zopatista.com wrote :
Anything else different? Did you make any performance comparisons
On Tue, Aug 28, 2012 at 12:31 PM, Vincent Pelletier vinc...@nexedi.com wrote:
...
I forgot in the original mail to mention that NEO does all conflict
resolutions on client side rather than server side. The same happens in
relStorage, but this is different from ZEO.
That's good. I'd like to
On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier vinc...@nexedi.com wrote:
We've just tagged the 1.0 NEO release.
any plans to support pypy in NEO? Once ZODB start to run on pypy it
would be cool to have relstorage/zeo or neo running on it as well.
--
Leonardo Santagada
Le 08/29/12 15:54, Leonardo Santagada a écrit :
On Mon, Aug 27, 2012 at 9:37 AM, Vincent Pelletier vinc...@nexedi.com wrote:
We've just tagged the 1.0 NEO release.
any plans to support pypy in NEO?
We're looking at pypy from time to time but there are at least 3 reasons
preventing us to use
