On Thu, 14 Jul 2011, Rainer Gerhards wrote:
I think I get the idea. To me, it looks much like a performance optimization. Please correct me if I am wrong, but I think the more important thing is to have block nesting. That, compared with substr() could probably get you somewhere. But I agree that user-settable variables would definitely a plus.
how would you grab everything before a '-' in the Nth word in a message today? I'm not sure it's possible (you can do a regex to grab the nth word, but then you can't do a substring or regex on that result)
I assume a local scope limited to the message being processed is sufficient. I also assume that there is no need to carry these variables over to an async action. Or is it? That would complicate and slow down things.
I think this would be specific to a particular message (i.e. they would be zero'd out when processing the next message), I could see this being used for an async action (basically in all the same places you would use an exiting property)
Do you think variables without block nesting make sense (this is the question if it is a v6 or a v7 feature)?
I don't see any reason why block nesting would be needed to make this useful. having these have a global scope, but not be persistant to the next message matches every case I can imagine. I don't see any reason you would need to limit the scope to a block given that there is only one pass through things for each message.
David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
