Please check the issue in our tracker to follow the progress: http://code.google.com/p/pharo/issues/detail?id=1884

For some platforms/configurations (IPv4 vs. v6) it is working (also depending on manually setting useOldNetwork). So there are many variables involved, which makes fixing difficult. But we will get there eventually. Any help welcome of course :)



On Wed, Mar 3, 2010 at 10:37 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Adrian did a change and asked for feedback. Not sure what happened.

On Tue, Mar 2, 2010 at 4:56 PM, Chris Muller <asqueaker@gmail.com> wrote:
> Hi Chris, thanks for your reply, I am aware of all the problems caused by
> the new NetNameResolver in Pharo.

BTW, I am not so aware of these problems.  Basic networking seems to
be so badly broken I am not even able to connect a socket, so I've got
to think any networking application, including even Seaside, would be
broken.  I'm surprised that such a breakage would be allowed to
persist in Pharo for so long.  Do you know what is going on and what
the plan is?
_______________________________________________
Magma mailing list
Magma@lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/magma