Re: [PHPiCalendar-DEV] File or DB driven? Or both?

[Marook Z. K. <ma...@cr...>]

Hi All.

Ok, I agree that the initial setup of PHP iCalendar should be=20
filebased. Basically, if files exist in the 'calendar' dir, show them=20
like it's done now. No challenge there.

The option, should be to enable database driven calendars.
Options for this, include a calendar submitted via FTP/HTTP/WebDAV to=20
the server. A calendar submitted this way, could be read-only in the=20
database, unless a new 'upload' is submitted.

Now, subscribing to calendars in the database, could be mush more=20
dynamic, than file based ones, since we can pass parameters to php that=20=

performs searches and maybe even date-range selections. The options are=20=

many, and I agree that we need to focus on main issues, but a move to a=20=

db would allow large-scale sites to support many users.

The admin-via-web aspect of a db driven calendar, would also make a=20
move towards enabling non-Mac/iCal users to maintain the calendar, and=20=

make them available to Mac/iCal users 'the cool way'.

And we don't need to generate files from the db, just a data-stream=20
when asked for it.

I haven't looked into how iCal askes for changes (HEAD request -> date=20=

changed-> download .ics..) or it simply downloads the files at=20
specified times. But having a LAST_CHANGED date field for the calendar=20=

would make this trivial.

Regarding XOOPS, yes this would make PHP iCal a module to XOOPS. I=20
don't know how much work this takes, but I assume it's mostly User &=20
Admin integration. XOOPS is also PHP/MySQL so should be possible. Maybe=20=

a branche?
I know XOOPS uses themes. I has User integration and web-based=20
admin/preference setup. All things PHP iCal needs, or has requests to=20
get.

Looking fwd to get my iBook back from repair, so I can dig into this...=20=

(Note, don't drop them on the floor from 2m. height...)


	Jakob Peterh=E4nsel

"A kiss is the proof, that the best in life, is found right under your=20=

nose"
Billie Jean Blanton

Email: ja...@hj...
AIM: Marook=