Howie et al,
> 1 - Event record storage
>
> i - In an ODBC Database
> ii - In a flat text file
I think that event records in an ODBC database is more flexible
because I could create my own interface for administering events
including creating an event to purge or clean up the events table.
> 2 - Event retrieval
>
> i - Internal fetches via ODBC
> ii - Fire off a Coldfusion template to retrieve events
A cold fusion template to retrieve events is again more flexible
because I could use any kind of storage system for key point #1. If
I wanted to use ODBC I could, or I could make my own flat file
format. The only advantage I could see for using internal ODBC is
that you wouldn't have to worry about CF being down when you try
to get your event list, but you could also use this mechanism as a
test for the CF server and re-start the service if it isn't working.
Earlier there was some discussion as to whether the service would
check constantly for new events or on some schedule, I think it
would be best to check on a schedule as a definable option to the
service. There could be a configuration GUI (or command line if
GUI isn't practical) that should let you define the interval for re-
checking the event list as well as an email address and message
to notify someone if the event list can't be retrieved over some
definable number of checks. It would also be nice to make it an
option as to whether it tries to re-start ColdFusion as well as an
additional option as to whether it should reboot the machine if it
can't.
> 3 - Types of events
>
> i - By frequency (every three minutes, for example)
> ii - Periodic by day (Each Monday at 3 PM, for example)
> iii - Periodic by Date (Each first of the month at 3 PM, for example)
> iv - All of the above
Hourly and Multiple hours of the day.
Also multiple days within a week.
In addition to these types of schedules I would also like to see
"One Time" events that would only be executed once, say for
kicking off some process that I don't want to run during normal
business hours.
> 4 - Format of database
>
> This is only important if the server should use ODBC directly. We need to
> decide the tables and DB fields required to implement the supported event
> types.
Addressed in #2
> 5 - Format of events from ColdFusion template
>
> This is only important if the server should use a ColdFusion template to
> retrieve events.
Since the event list will have multiple entries, it should probably be
a comma (or other delimiter) separated list of options for an event.
So, the real question is, what are the options necessary for
scheduling an event:
Initial Time: HH:MM:SS (24 hour time?)
Initial Date: MM/DD/YYYY (other date formats?)
End Time: HH:MM:SS (for stopping a scheduled event)
End Date: MM/DD/YYYY (for stopping a scheduled event)
Event URL: "http://blah-blah..."
Frequency: (M)ontly, (D)aily, (H)ourly, Mi(N)utes, (S)econds, (O)nce
Regularity: Which month, days, hours, seconds
(ie. "2" for every other day or "10" For every ten minutes etc.
You could also make this a little more flexible by allowing a list of
Months and Days such as "Jan,Apr,Jul,Oct" or "Mon, Wed, Fri")
That's My 2�
-Chris
������������������������ This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.CoolFusion.com/iMS.htm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
�����������������������==
