This Pythomnic [1] project -- that came up yesterday
in Daily Python -- is worthy to investigate.
I'll add it to the RPC Survey. By the way, that
will take longer too complete due to a project-boom
at the company this week.
[1] http://www.pythomnic.org/overview.html
cheers,
Senra
-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
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
|
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.
Secondly, zeo has a specific place and relationship. When I initiated
