Re: request for input re: OpenVPN API

I'm not an OpenVPN developer per se -- other than a few trivial patches 
-- but I should be able to comment.

First -- the requirements for what you want a VPN to do in a grid 
environment are something which need to be specified. Since OpenVPN is 
limited to either a 2-endpoint peer-to-peer model or a hub-and-spoke 
model, it isn't necessarily well-suited to cases where a arbitrary 
communications will need to be encrypted within a cloud.

Second, OpenVPN already provides a number of methods to interact with it 
which are readily programmatically accessible. This includes the manual 
page; OS-level signals; command-line and configuration file parameters; 
etc. My experience is that these are more than adequate for controlling 
the behavior which is presently available -- and that in cases where 
these tools and in of themselves don't provide the desired level of 
functionality, that building additional layers on top of the preexisting 
interfaces (rather than building entirely new interfaces) is appropriate.

Could you document the exact functionality you wish to add, and the 
business case for exposing that functionality as a native API?


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642