From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0bfa30b4e4570a291f4ea406d1a699db@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
From: rog@vitanuova.com
In-Reply-To: <c59798c7f2f4c588cd2cd337b831d30f@cwru.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 30 Mar 2004 17:07:24 +0100
Topicbox-Message-UUID: 4743ec76-eacd-11e9-9e20-41e7f4b1d025

surely rather than using the rather slow polling behaviour of tail -f
it would be better to have the files block on read until data is
available.

then you could just do:

	cat send & cat recv & cat status

no long latency on messages arriving, and you get the same
functionality.

also, if you've got a lot of traffic, you get correct interleaving of
messages, as the server controls the size of the data packets that cat
reads, which isn't the case for tail -f.

slightly harder on the server side, but not difficult, and a good
excuse to explore ways of structuring that kind of thing.