On Dec 17, 2013, at 10:06 AM, Alan D. Cabrera wrote:
>
> On Dec 17, 2013, at 9:38 AM, James Peach wrote:
>
>> On Dec 17, 2013, at 9:32 AM, Alan D. Cabrera wrote:
>>
>>>
>>> On Dec 16, 2013, at 7:47 AM, Leif Hedstrom wrote:
>>>
> On Dec 16, 2013, at 8:33 AM, "Alan D. Cabrer
On Dec 17, 2013, at 9:38 AM, James Peach wrote:
> On Dec 17, 2013, at 9:32 AM, Alan D. Cabrera wrote:
>
>>
>> On Dec 16, 2013, at 7:47 AM, Leif Hedstrom wrote:
>>
>>>
>>>
On Dec 16, 2013, at 8:33 AM, "Alan D. Cabrera"
wrote:
I'm writing a plugin that performs a recu
On Dec 17, 2013, at 9:32 AM, Alan D. Cabrera wrote:
>
> On Dec 16, 2013, at 7:47 AM, Leif Hedstrom wrote:
>
>>
>>
>>> On Dec 16, 2013, at 8:33 AM, "Alan D. Cabrera" wrote:
>>>
>>> I'm writing a plugin that performs a recurrent task, i.e. watches a file
>>> system for changes. What's the
On Dec 16, 2013, at 7:47 AM, Leif Hedstrom wrote:
>
>
>> On Dec 16, 2013, at 8:33 AM, "Alan D. Cabrera" wrote:
>>
>> I'm writing a plugin that performs a recurrent task, i.e. watches a file
>> system for changes. What's the best way to do this in a ATS plugin?
>
> Create a continuation an
> On Dec 16, 2013, at 8:33 AM, "Alan D. Cabrera" wrote:
>
> I'm writing a plugin that performs a recurrent task, i.e. watches a file
> system for changes. What's the best way to do this in a ATS plugin?
Create a continuation and schedule it to run every so often on a TASK thread .
You can a
I'm writing a plugin that performs a recurrent task, i.e. watches a file system
for changes. What's the best way to do this in a ATS plugin?
Regards,
Alan
