Robert wrote: >So to decide if a channel is due, just have to read an update_base, and add on the frequency * >period, then compare that calculated time to current time and see if it thus due.
>After the channel is updated, the update_base gets advanced by update_periods until its next >calculated due date is in the future. (The update_base doesn't just advance one update_period >alone, to handle the case where the computer has been abandoned for awile). >So the conduit would just write the new update_base key and it wouldn't be due. I think the above statments conflict. I think what you mean is that to decide if an update is due I just compare the update_base to the current time. Then after I do the update, I add on frequency * period to the current time and store it as update_base. Can you tell me if this is correct? Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
