Steve Parkinson wrote:
1) Private function definitions. SWIG can make wrapper functions for all
I am slightly in favor of explicitly listing the functions to export in
.i files.
3) NSS is a fairly object-oriented API. But, it lacks a formal
definition of the objects, and how they
Steve Parkinson wrote:
I like the way the .NET API is consistent, and whether you use C#,
Managed C++, or Visual basic, the API is always the same.
If we leave the OO implementation up to the scripting language wrapper,
then we will potentially have a different API for each language.
I
Jay Potter wrote:
Any suggestions on what I would need to do to get this implimented?
A lot of convincing that it is worth doing, to begin with. IMO,
pre-shared keys have no place in a general-purpose Internet browser such
as Mozilla. The authors of RFC4279 agree - see section 1.1 .
3 matches
Mail list logo
