[Accidentally sent this to Cyrus rather than to the list. Resending the next day.] Thank you very much (to David as well), I didn't realize I could create my own directory service and it would definitely simplify account management a lot. I just need to figure out on my side whether I want the server so tightly coupled to my application. I'm also on a different project to implement a reusable Calendar "Resource" and my initial thoughts were that many applications would use a single server for all their scheduling needs, but I hadn't addressed also using a single directory service, which both simplifies and complicates the matter. I'll think about it... Thanks again, Tyler On 18-Jan-07, at 3:59 PM, Cyrus Daboo wrote:

Hi Tyler,

--On January 18, 2007 3:44:23 PM -0600 Tyler Keating <tylerkeating@mac.com> wrote:

...

I'm currently building a web application that will use Calendar Server and I have one important question. What is the best way to create principal accounts on Darwin Calendar Server to match the member accounts of my web application? I'm open to any suggestions.

I do know that Cosmo Calendar Server has a Cosmo Management Protocol for remote administration, is there something similar for Darwin that I've missed?

The latest calendar server code has a generic directory module that can be used to populate accounts. There are several different implementations of this, including an xml file based variant, and open directory variant, and an SQL database variant. If your web app uses a directory or database of some form for its users and you can access that from "outside" then you could write your own calendar server directory implementation to get user accounts directly from there.

-- Cyrus Daboo

You don't need to restart the server when you edit the XML file; it re-reads it when the time stamp on the file changes. -wsv On Jan 18, 2007, at 5:10 PM, Brandon Keepers wrote:

I have this same need. Currently, I'm just generating and XML file every time a user is updated in the database, but that won't work in production because I don't want to be restarting the calendar server every 10 minutes.