Hi Sergei,

welcome back at OpenXPKI base,

OpenSSL 1.0 has been released this week, so GOST is no ghost anymore
in the western hemisphere, we should implement it fast now within
OpenXPKI. :-)

Sergei Vyshenski writes:
> In the early days of the OpenXPKI (Julia calls it just "ox" for
> short) a list of strategic development conventions was accepted
> (please find attached below).

Unfortunately "ox" has developed as a short form of OpenXchange -
(http://www.open-xchange.com/en) - a collaboration software,
at least here in Germany. So I'll still use the term OpenXPKI.

> Error handling should be user oriented, rather than developer oriented.

Yes. Yes. Yes. :-)

For OpenXPKI beginners the error messages are quite confusing,
so I'm glad Martin will make error handling much better in the
next half of this year. I look forward this will clear the way for
a broad new OpenXPKI user base.

The built in workflow engine provides a very flexible framework
for PKI rollout, so I really appreciate OpenXPKI.

> css and javascript browser-portable library.

I would be very glad if there would be an abstraction layer
to access the state engine with indivual own GUI needs
(customer A could prefer one page per question, customer B
could prefer all questions within one page, others would
like to handle the workflow via command line interface).
Perhaps the GUI/API/lib framework could be portable enough to 
approach to any of these needs.

Greetings

        -Achim

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel

Reply via email to