Le lun, 21/06/2004 à 17:31 +0930, Malcolm Caldwell a écrit : > What state information will be lacking? > > If the ldap server communicates with the gatekeeper you can find out > 1) if someone is on line > 2) if someone is in a current call > If we add a state notion to determine if somebody is currently in a call or not, we fall again in the non-standard case with non-standard attributes like with ILS. That's the only thing that should be missing though. H.350 defines a set of LDAP schemas permitting : - to H.323 clients to browse directories of H.323 people - to H.323 gatekeepers to use the H.350 scheme to authentify people There is no ntion of state, however you can use any LDAP attribute you want for the rest (comment, location, ...) Doing that would permit to have a big directory of GnomeMeeting users, but if we use the same LDAP repository to authentify and list people, then we won't have a way to know if somebody is online or not. That is well-suited for companies, but not for seconix.com. My idea was to : - have the static information of people and the authentication stored in a SQL database - the gatekeeper uses that database to authentify people - the gatekeeper reads the static information in the database and push it to the LDAP server when people login, and remove it when they logoff or when the gatekeeper timeout is elapsed Any comment? > What is needed is a gw between the gatekeeper and the ldap server. > opengk could be extended to 'publish' its state to the ldap server. > Alternatively the ldap server could query the gatekeeper for this > information. > -- _ Damien Sandras (o- GnomeMeeting: http://www.gnomemeeting.org/ //\ FOSDEM : http://www.fosdem.org v_/_ H.323 phone : callto:ils.seconix.com/dsandras seconix com
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=