mirror of
https://github.com/QuasarApp/qca.git
synced 2025-04-27 12:04:31 +00:00
A little extract from the mailing list.
svn path=/trunk/kdesupport/qca/; revision=366100
This commit is contained in:
parent
c72b66f323
commit
2b31e531fe
@ -35,6 +35,24 @@
|
||||
QCA_PLUGIN_EXPORT QCA::Provider *createProvider2() { return new P; } \
|
||||
QCA_PLUGIN_EXPORT int version() { return QCA_PLUGIN_VERSION; }
|
||||
|
||||
/** \page providers Providers
|
||||
|
||||
QCA works on the concept of a "provider". There is a limited
|
||||
internal provider (named "default"), but most of the work is
|
||||
done in plugin modules.
|
||||
|
||||
The logic to selection of a provider is fairly simple. The user can
|
||||
specify a provider name - if that name exists, and the provider supports
|
||||
the requested feature, then the named provider is used. If that
|
||||
didn't work, then the available plugins are searched (based on a
|
||||
priority order) for the requested feature. If that doesn't work,
|
||||
then the default provider is searched for the requested feature.
|
||||
|
||||
So the only way to get the default provider is to either have no other support
|
||||
whatsoever, or to specify the default provider directly (this goes for the
|
||||
algorithm constructors as well as setGlobalRNG()).
|
||||
*/
|
||||
|
||||
namespace QCA {
|
||||
|
||||
class RandomContext : public Provider::Context
|
||||
|
Loading…
x
Reference in New Issue
Block a user