Forum OpenACS Development: Scheduling/Unscheduling procedure

Is any chance to unschedule procedure scheduled with
ad_schedule_proc?

I checked source codes of utilities-procs and have not found any track of unschedule option.

I need to send notification emails in 2 hours and 15 minutes before meeting. Now I do it with ns_schedule_proc, but prefer to use ad_schedule_proc to see my procs in Monitoring package.

Is it possible to make time specific notifications with Notification package. I've not found docs for this package, but only API and was not able to catch all things just looking to the API. Any advices are appretiated.

Thanks
Denis

Yes, Andrew, that would be nice. If you don't save the id, I don't think there is any way to recover it later.

foreach item [ns_info scheduled] {
    # match on [lindex $item 8] break if found.
}

I've just unsaccessfuly spent more then a hour, trying to find any documentation for "ns_info scheduled". Where did you read about that feature?

It really works and returns a list of scheduled proc infos, but there is no any mention of "scheduled" option of "ns_info" in AOL docs (at least I've not found it). Can you please give me an advice where can I read about it.

Thanks

Thinking about this AOL Server option I got another question. If it's possible to use native AOLServer function to monitor scheduled procedures, do OpenACS really needs wrappers like ad_schedule_proc/ad_unschedule_proc?

There was no response to my proposals for rewriting scheduling stuff, so I've decided just extend the code from 4.6.1. I've just updloaded a patch with new function and some updates of old functions.

I still don't not like how this stuff is implemented, and hope to get any other opinions.

I also modified Monitoring package - added unscheduling option. Doing that I get another idea - what if add options like PAUSE, START, STOP. In this case all scheduled procedures will be always in the list, but not all will be runnig. It may be considered as "SERVICES".

That said, Dennis Khitrov's suggestion of relying on AOLserver's functionality, specifically the undocumented [ns_info scheduled], has a lot of appeal. It would be simpler and more robust than then current solution. But it would be a bigger change.