[Kroupware] IDEA: Kontacts has a field to specify where to download their Free/Busy

Jon Bendtsen jon at kollegiegaarden.dk
Tue Dec 23 21:21:22 CET 2003


tirsdag 23. dec 2003 kl. 14:45 skrev Bernhard Reiter:

[cut]

>>>> This means that someone, usualy the administrator, has
>>>> to download the Free/Busy lists for kontacts to the kolab server
>>>> before the user klients kan use them.
>>>
>>> The Free/busy lists are published by each single client.
>>> They push it to the server.
>>
>> yes, if they use the same server as me, i'm talking about remote
>> kontakts.
>
> I will still be fine with remote contacts,
> that each client pushes its free/busy information to one server.

look, pushing free/busy information to ONE server will not happen.
Company A will not push their info to Company B.


> A remote person than must find out where to get this freebusy list.

an entry in the kaddressbook, that the korganisor uses to lookup the 
information


> Thus it needs to be an entry in the Kolab Server LDAP addressbook.
> Subsequently KOrganizer will also have such an attribute.

i dont see why it needs to be centralised.


>>>> Why not add a field to the individual kontakts in the kaddressbook,
>>>> and then let the korganisor look up the needed information direktly
>>>> from the kontakt's information?
>>>
>>> This is planned in forthcoming revisions of Kolab
>>> that there is an entry in the ldap addressbook that points
>>> to the distribution of the freebusy list for this user.
>>> We believe it is a good idea.
>>
>> I believe that you misunderstood my idea. It's fine with all the 
>> people
>> working in the same company as me, which uses the same server, but
>> if i where to add you as a kontakt, a stranger, i want to be able to
>> specify
>> where your freebusy information is stored, so it can be retrieved when
>> it is needed.
>
> With my explanation above I think I've understood.
> My point being was that we need a corresponding entry in the
> addressbook for this to be neatly integrated in Kolab. :)

yes, the entry is needed, but only klient wise.



JonB



More information about the Kroupware mailing list