> On 29. Mar 2019, at 10:07, Sven Van Caekenberghe wrote:
>
> Holger,
Sven, All!
Thanks for moving it to GitHub!
Pharo Days:
I am in APAC right now and I am not sure if I make it. I am hesitating. Maybe
we can have a Google Hangout to discuss this (if not too inconvenient for the
ones
On Fri, 29 Mar 2019 at 18:08, Sven Van Caekenberghe wrote:
> Holger,
>
> I'll write most of my comments inline.
>
> Yesterday I moved my code to https://github.com/svenvc/NeoDNS using Tonel
> format, to make it a bit easier to consume. I also did a couple of minor
> updates while going over the
> The core cause of the problems is that the current NameResolver is totally
> blocking, especially in failure cases, which gives a terrible experience.
>
> One way to fix this would be with the concept of NetworkState, a cheap,
> reliable, totally non-blocking way to test if the image has a
Holger,
I'll write most of my comments inline.
Yesterday I moved my code to https://github.com/svenvc/NeoDNS using Tonel
format, to make it a bit easier to consume. I also did a couple of minor
updates while going over the functionality. Note the 'my code' is in the
package
> On 28. Mar 2019, at 08:02, Sven Van Caekenberghe wrote:
>
> Hi Holger & Norbert,
>
great. Regardless of how many versions exist. We should get one into the image
with proper platform integration.
I wasn't aware of your code but I assumed it is something you could write,
hence the
Hi Holger & Norbert,
Great, but ...
This did already exist in various forms, a couple of years ago I made a newer
version, they can all be found in http://www.smalltalkhub.com/#!/~BenComan/DNS/
- including unit tests (but some of the older code in there is a bit stale).
It covers most record
Norbert and me looked at using DNS for service discovery and ran into some of
the limitations of the NetNameResolver[1]. In the end I created an initial DNS
implementation in Pharo called Paleo-DNS[2] to overcome these.
DNS is a protocol we use every day but rarely think of. There is an active
