At 01:59 PM 09/14/00 -0400, you wrote:
> I have written a TCL/TK application that when called, invokes itself
>as many times as required to satisfy the original input parameters. The
>multiple invocations result in the first one starting as a master
>application and the remaining applications starting as slaves. All
>applications open a sockets. One for sending and one for receiving commands.
>
>
> The master starts and opens a socket listening for slaves to
>register. When a registration is received by the master it in turn sends a
>command telling the application to configure itself as a slave, basically
>disabling its GUI interface.
>
> The code has been tested and runs fine in a UNIX environment. I have
>wrapped the application using tclPro wrapper. The problem I have observed is
>when I take the same code and wrap it and run it on a Windows platform the
>communication channels do not appear to be working. The applications all
>start as expected, but there is no communication between the master and
>slaves.
>
> Is there something you need to do differently when using socket
>calls in a windows environment?
>
I have been able to port lots of tcl code that do sockets. They
run fine on windows (98/nt and above, but NOT w95!! - but I can't
get C code using sockets to work correctly on w95 all the time either).
I use the mktclapp wrapper, I don't know what the tclPro is.
One minor thought, is that the 2 systems do differ in line termination (nl
vs cr/nl) and
that if you are setting up a "line buffered" channel, you might
find you need to tweak something here. If you get this wrong, you could
hang waiting for a proper line terminator that won't arrive, so the get
won't return.
Also, go into an msdos window and enter "netstat -an" and see if
your servers are listening and if the connections occur.
eric
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/vtcl-user
