[Jens Vagelpohl]
>>> Does't the *already included* zeoup.py do exactly what you are trying
>>> to do? See the bin directory of your zope home.
[Sidnei da Silva]
>> Unfortunately no. It uses ClientStorage, which goes through the 1000's
>> of lines of the connection dance using connect threads and l
Sidnei da Silva wrote:
| Does't the *already included* zeoup.py do exactly what you are trying
| to do? See the bin directory of your zope home.
Unfortunately no. It uses ClientStorage, which goes through the 1000's
of lines of the connection dance using connect threads and large
timeouts. Eff
| Does't the *already included* zeoup.py do exactly what you are trying
| to do? See the bin directory of your zope home.
Unfortunately no. It uses ClientStorage, which goes through the 1000's
of lines of the connection dance using connect threads and large
timeouts. Effectively, ClientStorage w
On 2 Jul 2005, at 01:37, Sidnei da Silva wrote:
On Mon, Jun 27, 2005 at 02:38:48PM -0400, Tim Peters wrote:
| > Any suggestions about how to best implement this,
|
| Maybe just create your own socket, attempt to connect, and if
that attempt
| fails produce the kind of error message you want t
On Mon, Jun 27, 2005 at 02:38:48PM -0400, Tim Peters wrote:
| > Any suggestions about how to best implement this,
|
| Maybe just create your own socket, attempt to connect, and if that attempt
| fails produce the kind of error message you want to see? Of course if it
| succeeds, there's some chan
[Sidnei da Silva]
> We have a couple custom applications that use of zeo or just zrpc that
> would need a different connect strategy than what's provided as default.
>
> To be more specific, we need a way to try a connection and either connect
> or fail immediately with a reasonably short timeout a
