<br><br><div class="gmail_quote">2011/6/12 Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><div class="im"><div>On Jun 12, 2011, at 12:48 PM, Arnaud Quette wrote:</div><br><blockquote type="cite"><br><div class="gmail_quote">2011/6/12 Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex"> On Jun 11, 2011, at 3:53 PM, Arnaud Quette wrote:<br>
<br> <blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex"> * jNUT Java binding<br>
the exact content of this task is still to be defined, but this should include native client access and NSS support,<br> the following will be considered with a lower priority:<br> - device discovery (JNI using libnut-scanner),<br>
- configuration (using Augeas)<br> - mDNS discovery<br> I'm currently checking resources staffing with Eaton<br> </blockquote> <br> I'm not a huge fan of Java to begin with,</blockquote><div><br>so do I.<br>
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...<br> </div><blockquote class="gmail_quote" style="margin-top:0pt;margin-right:0pt;margin-bottom:0pt;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex">
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).<br>
</blockquote><div><br>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, ...)<br></div></div></blockquote><div><br></div>
</div><div>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.</div></div></div></blockquote>
</div><br>indeed, so let's go for native ;-)<br clear="all"><br>cheers,<br>Arno<br><br>