Hi everyone,
Martin and I are working on some optimizations for the workflow
context database. We want to split it into two databases, where one
holds the normal workflow data which typically consists of rather
small values (which can then be indexed which would make the joins
which are used for example in 'My certificates' much faster). The other
one would hold "bulk" data (such as certificate requests, certificates,
serialized data that could potentially be larger such as a serialized
list of subject alternative names, ...) and would not be indexed.
I've created a "blacklist" of workflow context keys that can potentially
get large for all of the workflows except for the LDAP publication
one, as I don't have a test setup for the LDAP publication (yes, I
had that planned someday, but as I did not need the feature, it fell
of the edge). Maybe someone with a LDAP publication setup (Sergei? :-)
could tell me which workflow context keys could become large and which
ones are just small strings or numbers ...?
Thanks,
Best regards,
Alex
--
Dipl.-Math. Alexander Klink | IT-Security Engineer
[email protected] | working @ urn:oid:1.3.6.1.4.1.11417
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
