[Nut-upsdev] 2.8.0 roadmap [jNUT]

[Charles Lepple]

On Jun 12, 2011, at 12:48 PM, Arnaud Quette wrote:

>
> 2011/6/12 Charles Lepple <clepple at gmail.com>
> On Jun 11, 2011, at 3:53 PM, Arnaud Quette wrote:
>
>  * jNUT Java binding
>    the exact content of this task is still to be defined, but this  
> should include native client access and NSS support,
>    the following will be considered with a lower priority:
>      - device discovery (JNI using libnut-scanner),
>      - configuration (using Augeas)
>      - mDNS discovery
>    I'm currently checking resources staffing with Eaton
>
> I'm not a huge fan of Java to begin with,
>
> so do I.
> but having played with Android a year and a half ago, and having  
> some requests more recently made me think we are still lacking a  
> Java binding...
>
> but if I had to interface a Java tool with NUT, I wouldn't want the  
> hassle of native bindings (i.e. JNI) unless it was absolutely  
> necessary. Most of the NUT protocol should be easily implementable  
> in pure Java (including SSL).
>
> indeed, native client access (ie implement the ascii NUT protocol in  
> Java) is easy enough to be implemented directly (as we have in  
> Python, Nagios plugin, ...)

Ah, I think we're saying the same thing. IIRC "native" in terms of  
Java is the underlying processor/OS, and I think you are describing a  
"pure Java" implementation.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110612/31476583/attachment-0001.html>