[Lognorm] [rsyslog] liblognorm

[Pavel Levshin]

Yes, for me it looks thread safe and reentrant.


--
Pavel Levshin


07.11.2013 20:35, Rainer Gerhards:
> Pavel,
>
> On Wed, Oct 30, 2013 at 8:51 PM, Pavel Levshin <pavel at levshin.spb.ru 
> <mailto:pavel at levshin.spb.ru>> wrote:
>
>
>     So, I have taken the opportunity and refactored liblognorm to use
>     json-c instead of libee. Some parts of libee now present in
>     liblognorm, notably field parsers and encoders. They were
>     rewritten to get rid of libee data structures. In the same time,
>     many bugs were fixed, and many were undoubtedly produced.
>
>
> I still didn't get a chance to merge, but you probably could lend me a 
> helping hand on a related topic. As you know, I am rewriting the 
> rsyslog core engine. The new engine has the capability to execute 
> action instances in parallel, one for each worker thread (wti).
>
> I am about to update mmnormalize to the new calling interface. The 
> question is if lioblognorm can be called concurrently (reentrant & 
> thread safe) with *the same* handle. That would obviously be best. 
> It's not (yet) documented to have this capability. However, if I 
> remember correctly, there is no problem in that regard. As you have 
> recently worked on probably the whole body of code, what's your 
> opinion on that? If we are not sure enough, we can always check later, 
> but I think if the first shot at the new mmnormalize implemtion should 
> better be on the safe side or not.
>
> Thanks,
> Rainer
>
>
> _______________________________________________
> Lognorm mailing list
> Lognorm at lists.adiscon.com
> http://lists.adiscon.net/mailman/listinfo/lognorm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.adiscon.net/pipermail/lognorm/attachments/20131107/1aa4b30a/attachment-0001.html>