[horde] What to do when removing user

Jan Schneider jan at horde.org
Mon Jun 28 00:43:26 PDT 2004


Zitat von pierre <pierre-henry.perret at noos.fr>:

> As the systme is data-driven, I suggest we could handle this directly in the
> model of horde database, which means that each horde module that
> plugs in must also plug in the data model.
>
> What you think ?

This is not the question, the remove-user-stuff is already API based. But we
still need to decide which data to remove in each application.

> ----- Original Message -----
> From: "Jan Schneider" <jan at horde.org>
> To: "Horde::Horde" <horde at lists.horde.org>
> Sent: Sunday, June 27, 2004 1:23 PM
> Subject: [horde] What to do when removing user
>
>
>> We are going to implement the application specific methods that get called
>> when a user gets removed from Horde.
>>
>> The correct thing to do was to remove *all* data this user created, but
> this
>> might also involve shared resources, like in Kronolith for example
> complete
>> shared calendars or single events in shared calendars.
>>
>> So the question is, should we do the "correct" thing or should we handle
>> this differentely, more graceful, whatever that means?

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting.php



More information about the horde mailing list