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?
Robert M. Bartis
Lucent Technologies *
PVG Testing
Room HO 2B-337
* 732.949.4565
* 800.759.8888 pin 1649486 / [EMAIL PROTECTED]
* [EMAIL PROTECTED]
HO Customer Support for external and OVT related issues:
> Hot Line: 732 949 1520 8 AM - 6PM EST
> 732 713 0257 6 PM - 8AM EST
> email: [EMAIL PROTECTED]
>
>
> PVG support for IEV/SIT issues:
> Monday - Friday (24 hrs.)
> 800.759.8352 pin 1739939 / [EMAIL PROTECTED]
> Saturday - Sunday (24 hrs.)
> 800.759.8888 pin 1649479 / [EMAIL PROTECTED]
>
>
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/vtcl-user
