On Tue, 2002-04-02 at 13:25, Chris Toshok wrote:
On Mon, 2002-04-01 at 06:34, JP Rosevear wrote:On Mon, 2002-04-01 at 01:11, Martin C. Messer wrote:JP, sorry, should have been more specific. If I want to store the FBURL in an LDAP entry for a contact (an entry that is not local to my addressbook), where should I store it? Put another way, if all my contacts are in a central LDAP database, how can the FBURL be stored on that contact record for correct retrieval by the scheduling feature of Evo?It should be FBURL, base on RFC 2739.That same rfc specifies the LDAP attributes to use, which we (sadly) don't use at the moment. I'll cook up a patch today. That RFC is what you should be going by, though.
OK, patch is ready (just waiting for review/approval.) The long answer to your original question is to use a schema like the attached (which I adapted from the RFC for use with my openldap installation here.) Does anyone know where to get this schema in some released form? With the patch evolution will notice the calEntry objectclass and if it's present will add it to the list of objectclasses of any object you create or modify with evolution. The only attributes we support after the patch are the single valued calCalURI and calFBURL attributes. url to the bug/patch is: http://bugzilla.ximian.com/show_bug.cgi?id=22965 Chris
Attachment:
calentry.schema
Description: Text document