On Wed, 20 Oct 1999, Magosanyi Arpad wrote:
> I think that the format for timestamp should be the return value of
> time(2) as a human readable integer, but in subsecond accuracy. Think
> about embedded systems and bandwith preservation, especially if we
> really want to put more timestamps into one message. Of course not the
> format of the timestamp is the most important issue of the protocol.
>
Same as I suggested. Sub-Second accuracy is nice-to-have, but somewhat
irritating on systems that do not provide it. I would suggest using an
optional fraction, separated by a period.
> It must be a single port one way tcp connection. One way means
> "one tcp socket", not "packets going only to one direction".
>
No, IMHO we want TCP _and_ UDP. I use two loghosts and many clients. That
would mean a large number of TCP connections. Please, allow UDP also.
Volker
--
Volker Wiegand Phone: +49 (0) 6196 / 50951-24
SuSE Rhein/Main AG Fax: +49 (0) 6196 / 40 96 07
Mergenthalerallee 45-47 Mobile: +49 (0) 179 / 292 66 76
D-65760 Eschborn E-Mail: [EMAIL PROTECTED]
++ Only users lose drugs. Or was it the other way round? ++
