-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 May 2006, at 02:57, David Pratt wrote:
Hi Jim and Roderigo! This is encouraging news. I have been putting
much thought into this also. There is a downside to refactoring ZEO
in that there are many folks heavily dependent on it and also
David Pratt wrote:
Hi Jim and Roderigo! This is encouraging news. I have been putting much
thought into this also. There is a downside to refactoring ZEO in that
there are many folks heavily dependent on it and also reasonably happy
with it.
The refactoring we are talking about won't effect
On Fri, May 05, 2006 at 07:25:50AM -0400, Jim Fulton wrote:
| IMHO there is no downside. People would be heavily dependent if they
| e.g. had programs directly interacting with ZEO internals, or
| subclassing ZEO components. I would bet the number of people who are in
| that position can be
Hi Florent
| For the values stuff, what people usually do is have two BTrees that hey
| keep in sync, one being the reverse of the other. Finding all values = X
| is then simply a matter of using the proper API on the reverse Tree (and
| it's fast).
Ok, thanks. People on zope-dev pointed me to
Sidnei da Silva wrote:
...
Oh, if I'm allowed to speak *wink*, it would be great if in this
refactoring 'zrpc' could be made to work with less dependencies.
I'm using 'zrpc' on a project and it was a pain to implement a
minimally working application because it depended on a few convoluted
On Fri, May 05, 2006 at 10:32:12AM -0400, Jim Fulton wrote:
| Sidnei da Silva wrote:
| ...
| Oh, if I'm allowed to speak *wink*, it would be great if in this
| refactoring 'zrpc' could be made to work with less dependencies.
|
| I'm using 'zrpc' on a project and it was a pain to implement a
|
