views:

23

answers:

1

We have a web-based calender App, which was written long before I was hired by our company. It uses a proprietary system (our own) to store and work with them. I was told it wasn't that bad of an App back in the day, but with the inception of web calendars (notably Google Calendars), it just seems outdated and unusable.

Our boss wants us to rewrite this any time soon, so I am doing a little research on it. Since he wants to use an open standard for our new calendar webapp, he suggested Apple's iCal Server. We mainly use Linux Servers and use mod_perl for the programming, which isn't iCal's native environment. On the other hand, iCal seems to be capable of everything we have on our checklist.

Mandatory list of things it should be capable of:
* Collaborative sharing of calendars
* At the same time, access restriction must be highly customizable so it can be manipulated with our already present Access Control List
* Possibility to sync it to any device (with any OS)
* Manage multiple users
* Good API so we can manipulate the server almost entirely over the API (except for maintenance)

It would be favorable if there are perl modules that help us in rapid deployment.

So, since I value Stackoverflow's opinion on good practices, I ask you guys opinion. If you think that an other CalDAV Server would be better, I am open for suggestions :)

I marked this as a community wiki, since I believe there is no 100% right answer.

A: 

iCal is an excellent choice for your scenario.

There are lots of helpful libraries for manipulating iCal calendars in Perl: http://search.cpan.org/search?m=all&q=ical&s=1&n=100

DAViCal is an open source server with web-based management. It uses PHP, but may still be useful depending on your options: http://www.davical.org/

thesuperbigfrog