Also, can we please have that code put into VIFF? I don't like it
that we're getting more and more "secret" code floating around :-)
Especially not when we make changes to VIFF to accomodate this
secret
code -- it would be different if we had simple drop-in Python
replacements for it.
(I know you've said that this code can be made public since it's
part
of NaCL, so this is more for the record...)
The code will not be a part of VIFF, but a prerequisite like Zope
interfaces or Twisted.
Why is the code not put into VIFF? We already have too many
dependencies, to I would much prefer not to add new ones.
Dependencies are especially a problem on Windows, unless they come
with
ready-made installers with the compiled C extensions.
I am not sure. Reading http://nacl.cace-project.eu/features.html I see
that there are no copyright restrictions on the NaCl code.
____________________________________________________
Janus Dam Nielsen
Research and Innovationspecialist, PhD.
CENTRE FOR IT-SECURITY
THE ALEXANDRA INSTITUTE LTD.
T +45 42 22 93 56
E janus.niel...@alexandra.dk
W alexandra.dk
____________________________________________________
_______________________________________________
viff-devel mailing list (http://viff.dk/)
viff-devel@viff.dk
http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
