> 1 - Event record storage
>
> i - In an ODBC Database
> ii - In a flat text file
Database is preferred.. if you wanna use XML.. I'd say it could be
stored in the DB as well.. but text seems very limited
If you aren't going to use ODBC, you'll have to write parsers for that
text file.
>
> 2 - Event retrieval
>
> i - Internal fetches via ODBC
> ii - Fire off a Coldfusion template to retrieve events
Internal fetches would be cool.. but seem limited.. a template would
allow you to take the standard format and "massage" it more if you so
desired.. also, a template would let you be able to usea text file or
db, would it not?
>
> 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
All.. for sure.
> 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.
I think if we go the template route, this is less important as the
developer can decide how they would like it to work.
> 5 - Format of events from ColdFusion template
>
> This is only important if the server should use a ColdFusion
template to
> retrieve events.
Not sure I see the need for this.. wouldn't the template execute
whatever code it needed against the CF engine?
Well, just my 2 cents worth...
Greg
========================================================================
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/
========================================================================
