[dev] [cvs] commit: turba/lib Turba.php base.php turba/lib/Driver imsp.php share.php

[Chuck Hagenbuch]

Quoting Michael Rubinsky <mike at theupstairsroom.com>:

>> If this is the only holdup, then I don't think this is that much of a
>> problem - changing the use_shares source _is_ changing the source of
>> the contacts in it, and if we could have an upgrade or "switch" script
>> for it.
>
> Ok.  The only gotcha here is that any upgrade script wouldn't be  
> able  to update sources that need a user login...like IMSP.  But I  
> guess as  long as we document this somewhere at least admins will  
> know.

I'm not sure I think this is a good idea, but for those kinds of  
shares you could set a flag on the share itself telling it that the  
next time it's loaded with proper perms, it needs to update itself.

>> That doesn't seem so bad. I've already resigned myself to/figured out
>> that having some sort of "params" is necessary, so if any info like
>> this goes here, that's better. Still lets us use autoincrement ids for
>> shares with a future straight-sql share driver. :)
>
> Cool. I've suppose it's also worth mentioning that I've been going   
> under the assumption that we still need to create the md5(mt_rand())  
>  style keys from Turba since there's no bc way to have the share  
> system  create it's own keys at this point...

Well, we could have the share system ignore the provided keys. :)

-chuck