You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO, there's little reason to split the implementation in two for #-ipv6 and #+ipv6 (openmcl.lisp vs clozure.lisp).
In any case, when #+ipv6, if there is no server behind the IPv6 address, try the IPv4 address!
eg. in clozure.lisp (perhaps other places would apply too):
The text was updated successfully, but these errors were encountered:
informatimago
changed the title
When #+ipv6 also try to resolve an IPv4 address if the connection cannot be established with the IPv6 adderss.
When #+ipv6 also try to resolve an IPv4 address if the connection cannot be established with the IPv6 address.
Oct 25, 2021
I remember the #+ipv6 division in clozure.lisp was mainly to separate code for CCL 1.11 and all prior versions (<=1.10) which doesn't support IPv6 at all. CCL push :clozure and :ipv6 into *features* only since version 1.11, and usocket uses this observation and to select "modern" code for certain functions for CCL 1.11 afterwards. So this is basically a historical and compatibility reason.
Consider this issue closed since there's no bug reported here. I think it's better to keep the current design to make sure usocket continues supporting all historical CCL / OpenMCL versions, e.g. very old versions for PPC Mac OS X.
Related to #66
IMO, there's little reason to split the implementation in two for #-ipv6 and #+ipv6 (openmcl.lisp vs clozure.lisp).
In any case, when #+ipv6, if there is no server behind the IPv6 address, try the IPv4 address!
eg. in clozure.lisp (perhaps other places would apply too):
The text was updated successfully, but these errors were encountered: