Hi there, I'm not so sure this is the right forum to discuss these matters, 
but I'm curious and I know there are some fine folks around here who might 
have various interests so here we go :)

I'd like to build an event driven API based engine to work with, but not 
exclusively, syslog messages as actuators. That would be a first experience 
with Mojo::IOLoop for me, but it seems appropriate for this project.

The part I'm wondering about is how to capture relevant syslog messages. I 
have rsyslogd on the server already listening and configured with filters 
for message forwarding. Would that be the correct way to achieve this ? 
Messages should be forwarded to a socket that could parse them (Sys::Syslog 
or such?) and act upon ?  Or are there modules in the framework I could use 
for that purpose ? 

I need guidance on this, any relevant comment would be highly appreciated.

Cheers,

Luc

-- 
You received this message because you are subscribed to the Google Groups 
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

Reply via email to