See if something like this might help:
((NetNameResolver addressesForName: 'squeak.org')
detect: [ :info | #inet4 = info addressFamilyName ])
socketAddress hostNumber
Calling a resolver can be slow, so you'll want to remember the result,
and maybe put it in a #startUp: method.
We should revisit the networking stuff after the 5.3 release. Ian wrote
the primitive support ages ago, and at some point I mashed it into the
trunk. But there were concerns about performance of the resolver (at
least on Windows) so we ended up leaving "Enable IPv6 and new network
support" as a preference. Maybe it's time to turn the preference on,
work through the issues, and get rid of the old networking stuff.
Dave
i
On Thu, Nov 28, 2019 at 02:04:36PM -0800, tim Rowledge wrote:
> Yeah, I know about the occasional issue there and perhaps it's the problem here. The interesting question is why my Pi has no problem whatsoever (maybe it has just the one ethernet thing?) but the mac & linuxX86 machines do.
>
> Then the question for more practical purposes is how one can get any sort of meaningful IP number to satisfy the needs of a squeaksource server running on said linuxX86 machine. Setting it explicitly is terribly unsatisfying and of course unstable in the face of dhcp setups.
>
> Also, if we can't have workable solution then we should probably remove the code that appears to provide one!
>
> > On 2019-11-27, at 6:24 PM, Chris Cunnington <
[hidden email]> wrote:
> >
> > Perhaps you would like to read this thread. I think the upshot is that you are expecting consistency where none is possible.
>
> tim
> --
> tim Rowledge;
[hidden email];
http://www.rowledge.org/tim> Fractured Idiom:- COGITO EGGO SUM - I think; therefore, I am a waffle
>
>
>
Locked
