RE: iocLogServer change?

["Liyu, Andrei" <liyua@ornl.gov>]

	About future ...

	I agree with current situation. Server (IOC) has Error thread.
Error thread gets messages and sends to Error server. 
	+ Error server holds some latest messages (quantity & time) in
buffer. Also there is "central" Error client to read messages from Error
server.
	Message should have structure (as minimum field divider). So
client can sort and show messages by time, IOC, field.
	It seems Error, Archive, Alarm mechanism have similar behaviors.
Of course, IOC server layer should have configuration for Error, Archive
and Alarm threads priority, buffer. Maybe archive thread will have more
priority for diagnostics systems. But alarm and error threads have more
priority for technology systems. 
	Maybe it should be solved on CA level. It is correct to have
once protocol per server. For example, OPC has data, alarm, history
protocols.

Thanks, Andrei.

-----Original Message-----
From: Allison, Stephanie [mailto:saa@slac.stanford.edu] 
Sent: Wednesday, July 13, 2005 4:03 PM
To: EPICS tech-talk
Subject: iocLogServer change?

Hi All,

We're looking at upgrading iocLogServer so that it either writes
messages to a file, like it does now, or forwards the messages to the
cmlogServer (which would make iocLogServer be a cmlog client).  We think
it's easier to do this than to port the CMLOG client and daemon, and
particularly ACE, to our RTEMS IOCs.  Part of this effort would also be
to add support for messages that contain both ASCII text and other ASCII
"tags" like facility, status, severity, and task name.

Any comments?  Dumb idea?  Anybody interested in something like this?
Should it be done in such a way that it can go into some future EPICS
base version with the new features enabled via some configure file?  Or
left unbundled?

Thanks,

Stephanie Allison
SLAC/SSRL, SLAC/LCLS