[ZODB-Dev] Really want to refactor ZEO's networking archiecture

[Rodrigo Dias Arruda Senra]

[ Jim Fulton <jim at zope.com> ]:
----------------------------------------
|  
|  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 reuse judgment day. 

 I'll invest some time along this week (and probably the next too)
 to make a survey [1], as complete as I am able.
 Any feedback or contribution is very welcome.

 About Jim's proposed API [0], Twisted has the equivalent syntax:

 [Jim's]    def input_data(connection, data): pass
 [Twisted]  def dataReceived(self, data): pass

 [Jim's]    def connection_closed(connection, reason): pass
 [Twisted]  def connectionLost(self, reason): pass

 [Jim's]    def close(): pass
 [Twisted]  def loseConnection(self, connDone): pass

 [Jim's]    def connected(connection): pass
 [Twisted]  def connectionMade(self): pass

 [Jim's]    def failed_connection(reason): pass
 [Twisted]  def clientConnectionFailed(self, connector, reason): pass

 The model is a little bit different (I plan to cover it in the
 survey), but we can notice the similarity. It is probably *too soon*
 to ask this, but independently of Twisted adoption or not,
 would it be desirable to mimic Twisted name conventions ?


 [0] http://svn.zope.org/ZODB/branches/network/notes.txt?view=markup  
 [1] http://www.zope.org/Members/rodsenra/RPCSurvey
 [2] http://twistedmatrix.com/documents/current/api

cheers,
Senra

-------------
Rodrigo Senra
rodrigo.senra.nom.br