Tickets :: Comment on [#13730] Implementation of peer verification in TLS connections

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ .__. __..__ [__)\| \\| \|(__ [__) [__)\|__/\|__\.__)\|
Comment	>> I see the point that an independent library must not rely on horde's >> configuration. However, I see no point in storing the same >> information multiple times. As long as the Socket Client library is >> used within horde, horde's configuration will be available. Therefore >> this information should be used if its available. > > That's fine to want to not reproduce configs, but you simply can't > assume globals exist outside of Horde applications and Horde_Core. > The presence of $conf is 100% reliant on Horde_Registry being both > available and invoked. > > So this is getting better, but there simply cannot be any reference > to global variables in Socket Client code. These dependencies must > be injected into Socket Client solely by configuration parameters. > This is the whole point of Factories and dependency injection (see > Horde_Core). In fact, much of Horde can be seen as the configuration > layer to our various libraries.
Attachment
Watch this ticket