Hi!
I would like to write a small daemon that monitors (tails) a server log,
parses the entries and sends HTTP requests based on some of those entries. I
would like it if the reading of the log file and the sending of http
requests were asynchronous. Should I use twisted for this? Or is twisted
ov
Thanks! Your advice is much appreciated.
martin
On Wed, Aug 26, 2009 at 10:08 PM, Glyph Lefkowitz
wrote:
> On Wed, Aug 26, 2009 at 9:54 PM, Cary Hull wrote:
>
>> It would certainly be nice if Twisted supported async file io, but in this
>> case wouldn't a ProcessProtocol around 'tail -f' be a g
I am using linux, and I want the daemon to be as responsive as possible to
log events, so I think I would rather have it sit on the same box as where
the log is produced. (Perhaps I'm wrong about this?) So I'm going to try
Cary's ProcessProtocol approach, and if that doesn't work, Glyph's
LoopingCa
PyInotify only allows you to detect file changes, leaving you with the task
of asynchronously sending http requests.
-martin
On Thu, Aug 27, 2009 at 12:19 PM, Mikhail wrote:
> Martin-Louis Bright gmail.com> writes:
>
> >
> >
> > I am using linux, and I want the da
hi!
Which is the recommended or preferred way to deploy an app that will
leverage twistd: designing the app as a twistd plugin or creating a Service
and using a .tac file?
Also, if you need to expose your functionality as a Service to properly use
the twisted application framework, how do you achi
oing my work
>> using the process protocol and tail -f but needed the software to work
>> on 3 versions of linux and os x. The read() way of doing it was
>> ultimately the most cross platform way I could come up with. Good
>> luck.
>>
>> -rob
>>
>>
>
