Re: R3.14.8/logClient

[Marty Kraimer <mrk@aps.anl.gov>]

Benjamin Franksen wrote:

> Hello,
>
> I am in the process of porting CaPutLog [1] to R3.14 and noticed that 
> the implementation relies on an almost identical copy of the R3.13 
> logClient library (part of libCom). I further noticed that the 
> logClient in R3.14 is *almost* fit to be re-used for CaPutLog. I have 
> made some rather superficial changes to logClient.[ch] that would 
> enable such a re-use. The only change in the interface is an additional 
> extended initialization routine
>
> epicsShareFunc logClientId epicsShareAPI logClientInitExt (
>    struct in_addr server_addr, unsigned short server_port);
>
> that enables creation of a client that send messages to a different 
> server. Additionally, this init routine does /not/ automatically 
> register with the errlog library, i.e. it does not call 
> errlogAddListener.
>
> Since all existing routines remain unchanged, this change would be 
> completely backward compatible.
>
> Are there any chances to get this into R3.14.8? If yes, to whom should I 
> send the patches?
>
> [1] http://www-kryo.desy.de/documents/EPICS/DESY/EpicsLog/CAPutLog.html
>
> Ben
>  


Perhaps it could go into 3.14.8 or 3.14.9

Send me your version of logClient.h and logClient.c so that I can take a 
look.

Also

1) what changes are needed for the Application Developers Guide?
2) What should be added to the release notes?

Marty