2009/7/22 Schwab,Wilhelm K <bschwab@anest.ufl.edu>:
Sig,
Queue veryLoudHeadSlap.wav - however, that is not a fix for it on Linux. Â Also, on Windows, I am not getting the fully qualified name, which is another problem. Â It also helps make the case for formalized session management, as the image should know when it has had its first cup of coffee (the vm can inform it).
Usually, all code , working with sockets , sending #initializeNetwork, to be sure it is initialized: Socket>>newTCP: family "Create a socket and initialise it for TCP" self initializeNetwork. ^[ super new initialize: TCPSocketType family: family ] repeatWithGCIf: [ :socket | socket isValid not ] --------- Socket>>initializeNetwork "Initialize the network drivers and the NetNameResolver. Do nothing if the network is already initialized." "Note: The network must be re-initialized every time Squeak starts up, so applications that persist across snapshots should be prepared to re-initialize the network as needed. Such applications should call 'Socket initializeNetwork' before every network transaction. " NetNameResolver initializeNetwork ---------- another way could be just add the #startUp method and initialize network there. But i think that current solution is more elegant, because if your image never using the network, it will never initialize the plugin and in this way, preserve some resources. And , of course , there could be the cases, where VMs built without network support, or running with disabled networking security setting (for sandboxing). In these cases this primitive (as well as rest of socket prims) will fail. As for retreiving a fully qualified name - can't give you answer right now. I think it can be answered by Andreas, who added the ipv6 support recently to Windoze VM platform code.
Bill
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Tuesday, July 21, 2009 6:53 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows
Guys, see my comment on that issue.: #localHostName should not be used before #initializeNetwork.
Hope it helps.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.