On Friday 01 August 2003 05:43, René Fournier wrote:
[snip]
> I know, but I'm not talking about writing to the socket, just echoing
> to the local Server command line. I would expect the echo'd text to
> appear in the server terminal window as the script runs--but it only
> appears when the serve
On Thursday, July 31, 2003, at 02:45 PM, Chris Shiflett wrote:
--- René_Fournier <[EMAIL PROTECTED]> wrote:
Is it normal for a socket server to output all the echo'd
messages only after the socket terminates?
Can you explain what situation you're trying to describe? For example,
echo
does not wr
--- René_Fournier <[EMAIL PROTECTED]> wrote:
> Is it normal for a socket server to output all the echo'd
> messages only after the socket terminates?
Can you explain what situation you're trying to describe? For example, echo
does not write to a socket, so there's more going on than you're telling
Is it normal for a socket server to output all the echo'd messages only
after the socket terminates? According to the source code, I would
think that during its execution any echo "text"; commands would output
to Terminal, but in practice (at least under Mac OSX), it's only after
the Socket ter
4 matches
Mail list logo
