Tickets :: Comment on [#5175] Restructuring the Kolab driver

* Your Email Address
* Spam protection	Enter the letters below: _____ __ ____ ___ _ _____ \| __ \\| \/ \ \ / / \| \| \|/ ____\| \| \|__) \| \ / \|\ \ /\ / /\| \|__\| \| \| \| ___/\| \|\/\| \| \ \/ \/ / \| __ \| \| \| \| \| \| \| \| \ /\ / \| \| \| \| \|____ \|_\| \|_\| \|_\| \/ \/ \|_\| \|_\|\_____\|
Comment	> Lack of stability of the older driver was the reason for choosing > this solution. If you feel that is not ok I think there are two > possible alternatives: > > > > 1) adding this as a second possible Kolab driver (as kolab2.php) > > > > or > > > > 2) having the old and the new driver in the kolab.php class with a > wrapper that decides automatically based on the capabilities of the > Kolab module
Attachment
Watch this ticket