datasocket localhost faster than network name

[Davediego]

When I set my datasocket urls to dstp://localhost/var instead of dstp://machine_name/var the various connections are made MUCH faster. When using localhost, all variables seem to connect instantly, while if I use machine_name instead, it seems to make about 1 connection per second (I'm just watching the led indicator change to green) and so if I have a bunch of variables connecting, it can take quite awhile. I can use localhost on the server machine, however I need to be able to make fast connections on the client machine, and so I have to use machine_name. Is this some inherrent flaw in datasocket? Is there a workaround, or could I have a poor network driver?

[Davediego]

also if I use the ip address, I get the same poor connecting performance as using machine_name

[chutla]

Greetings!

"Localhost" does not require any name resolution...it is a "builtin" name in a windows environment. A "real" machine name requires name resolution,which always requires some time. You might try assigning your own machine as the name resolver. (YOu might need to poke around to see what machine on your network is really performing the name resolution.)
Alternatively, use the IP address instead of the machine name.

Just a few suggestions...

Eric

[Davediego]

well, I tried using IP addresses and had the same result. Ultimately the datasocket apps will be running on a 3-4 system lan, connected by a switch. There will not be a DNS server present in this lan (nor is there one now as I am testing). Again IP addresses are just as slow as using machine network ID's. Any other ideas? Thanks.