|
|
On May 29, 11:26 pm, Rolf Schroedter <m...@xxxxxxxxxxx> wrote:
> You need to setup a server socket on host2:
> socket -server host2 19000
>
> Stuart wrote, On 30.05.2008 10:36:
>
> > Perhaps somebody can help me understand this behavior..
>
> > On host1 inside the tcl shell I type
>
> > set s [socket -async host1 19000]
>
> > I get an error "couldn't open socket: connection refused". This I
> > expected
> > as I have no server listening on host1:19000
>
> > On host2 inside the tcl shell I type
>
> > set s [socket -async host1 19000]
>
> > and I get "sock5". There is still no server listening on host1:19000,
> > and so I'm
> > wondering why on host2 I don't get the "couldn't open socket:
> > connection refused" message?
>
> > Thanks in advance,
>
> > Stuart
Thanks Rolf.
I'm trying to create a TCL/TK GUI that talks to a calculation engine.
The engine supports
multiple clients through sockets, and the TCL/TK clients do not have
to necessarily run
on the same host that runs the calculation engine.
I am trying to get a handle on the various failure modes, for example
calculation
engine not running hence nothing to connect to.
So I was surprised, that if the calculation engine was not running, I
observed different
behaviors if I tried to run the GUI on host1 and connect to port 19000
on host1, vs. running
the GUI on host2 and trying to connect to port 19000 on host1.
Maybe its late at night and I'm missing something simple. At any rate
I'm puzzled for now.
Stuart
|
|