On Sun, 2 Feb 2003, Bruce Momjian wrote:
> Kurt Roeckx wrote:
> > On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
> > >
> > > Sure. But you still want to be able to say (and can say, in some [many?]
> > > socket API implementations) that you want to accept only IPv4 or only IPv6
> > > connections. I also want to be able to say the same thing in my database.
> >
> > You just create either an ipv4 or ipv6 socket. And then you can
> > bind to an address of that type if you want. Either all
> > addresses or a specific one.
> >
> > Depending on the OS, binding to all addresses on IPv6 will also
> > bind to all the ipv4 addresses, which can be both handy an
> > annoying. On others you need 2 sockets if you want to listen on
> > both ipv4 and ipv6, which makes more sense.
>
> Well, that's interesting. Current CVS only binds to IPv6, and assumes
> IPv4 will work too. If some OS's require a separate Ipv4 binding, we
> are going to hear about it before 7.4:
I don't think we should listen on IPv6 just because it is supported. It
should be a configuration variable:
tcpip_socket = true
ipv6 = true
Gavin
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
