We have this one client who is presently managing bookings for event spaces with an excel spreadsheet. This poor man highlights by hand the hours he needs and names them by day, etc. Every time someone wants to book, he looks it up click click click click and hopes that his paper version, computer version, or whatever... is recent. I could export all with some level of error, into a sensitively formatted data set.

A lot of people have already existing calendars. The only stability I have seen is the ical standard .. Mozilla Sunbird is coming out.

With a method that uses the ical standard.. Your gold client, this events organizer.. a beauty salon manager.. would all be able to (if they want) enter the changes in their laptop, and a script could regulalry update the website ical file or records- from their data.

I am thinking my problem separates into two things that could be re-used. One is a table layout for mysql for the ical standard (which I can't see an example of).
The other is a time collission detector.

The tie collission detector could simply be.. if we have unix time 23 through 32 (excuse me).. and an inquiry for time 31-34 was made.. we can simply detect that $requested_start < $last_registered_end Thus a collission is present.

I am using CGI::Application, HTML::Template, and CGI::Session. I was hoping to use Calendar::Schedule, but it's kinda buggy- or super duper unfriendly to develop with.

I'm gonna offer the project up for grabs when done, so nobody has to do this again!!! :) </p