Dirk Meyer wrote:
> Duncan Webb wrote:
>> OT: A big assumption that broadcasters transmit on time, there is nearly
>> always a couple of minutes betweens shows, but when they do then 15 secs
>> lead-in is better than missing the beginning.
>>
>> You don't have to follow my syntax could do it like:
>> | t = CronTimer(callback)
>> | t.at((min=15,sec=30))
>> | t.at((min=20))
>> | t.list() => [ "*:15:30", "*:20:00" ]
>> | t.remove(t.list()[0])
>> | t.list() => [ "*:20:00" ]
>
> If you read my mail again, I had something similar in the interface :)
> So yes, it is a good idea to add seconds ;)
I meant when you set the time, to me:
| t.at((min=15,sec=30))
is clearer and more explicit than
| t.at("*:15:30")
or to run something every 15 minutes
| t.at((mins=15))
by making it plural.
Only an idea.
OneShot is always better than At with a repeat flag.
Duncan
BTW what do I have to about the client side of the connection, reading
the doc string didn't help me too much. A quick search for an example
left me even more confused.
I would like to return the state of the connection, if the server is down.
Wait for the async call is completed before returning from a sync function.
Thanks
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
