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
--
[ Jim Fulton <[EMAIL PROTECTED]> ]:
|
| Some notes on this can be found at:
|
| http://svn.zope.org/ZODB/branches/network/notes.txt?view=markup
I volunteered to give some input about what is going on inside
Python's RPC World, food for the reus
Some notes on this can be found at:
http://svn.zope.org/ZODB/branches/network/notes.txt?view=markup
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com h
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
|
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
step
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 ca
Jens Vagelpohl wrote:
-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 depend
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 t
Rodrigo Dias Arruda Senra wrote:
...
I volunteer to help with two-hours time slices on a daily basis,
probably more on weekends.
Great. We should figure out a time to discuss what we're going to do.
I can often be found on the #zope3-dev irc channel. Otherwise,
I'll start some email discuss
-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
re
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
[ Jim Fulton <[EMAIL PROTECTED]> ]:
| I'd like to do all of these things, but the main reason to refactor
| ZEO's networking architecture is to make it testable.
|
| Writing ZEO tests now requires actually starting servers and
| clients. This is nuts.
I think that my next big project might be to
refactor ZEO's networking architecture.
Wonder what the main reason is?
- Provide more secure connections? Nope
- Leverage Twisted? Nope
- Get rid if the insane async/sync client madness? Nope
- Get better storage-server performance? Nope
- Allow sim
13 matches
Mail list logo
