Re: opening a connection with more than a single server

[Jens V. <je...@zo...>]

we can close the thread, that's fine. for me it was just an interesting=20=

tidbit that someone else revealed to me.

i still maintain that the discussion about ldap.open back in january was=20=

for totally different reasons and doesn't really have any bearing on =
this.

jens

On Thursday, May 2, 2002, at 12:41 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
> > ldap.open doesn't have anything to do with this as
> > far as i know.
>
> It has. Please think again.
>
> > actually, it now even seems to be supporting two ways to
> > get a connection:
> >
> > ldap.open( 'server:port' )
> > ldap.open( 'server', port )
>
> Note: The exact declaration is currently:
>
> def open(host,port=3D389,trace_level=3D0,trace_file=3Dsys.stdout):
>
> > the only item (for this discussion) that i am looking it is the
> > string 'host'. i know that under 1.10 i could do..
> >
> > ldap.open( 'host1 host2 host3' )
>
> Which is not possible with separate key-word parameter _port_ in
> function parameter list of ldap.open().
>
> > assuming they all run on the default port. i'm not interested
> > in non-default ports here.
>
> Are you kidding?
>
>  > don't get me wrong, i am not trying to warm over some ldap.open
>  > declaration semantics.
>
> If it's just an interesting thing go and use ldap.initialize() and
> we'll close this thread.
>
> Ciao, Michael.
>