<p dir="ltr"><br>
On Feb 25, 2015 8:22 AM, "Jeffrey Hutzelman" <<a href="mailto:jhutz@cmu.edu">jhutz@cmu.edu</a>> wrote:<br>
><br>
> On Wed, 2015-02-25 at 07:42 -0800, William Roberts wrote:<br>
> > On Wed, Feb 25, 2015 at 7:28 AM, Ludovic Rousseau <<br>
> > <a href="mailto:ludovic.rousseau@gmail.com">ludovic.rousseau@gmail.com</a>> wrote:<br>
> ><br>
> > > 2015-02-25 12:16 GMT+01:00 William Roberts <<a href="mailto:bill.c.roberts@gmail.com">bill.c.roberts@gmail.com</a>>:<br>
> > > > That's from the client application side. I was looking for a java<br>
> > > binding to<br>
> > > > the ifd interface.<br>
> > ><br>
> > > Why do you want to call the IFD handler directly from Java?<br>
> > > Why not use the PC/SC interface?<br>
> > ><br>
> ><br>
> > I am not explaining this properly :-P<br>
><br>
> Perhaps not.<br>
><br>
> I think what you're asking for is effectively the ability to write an<br>
> IFD handler in Java. For pcsc-lite, I don't think that's realistic --<br>
> it would mean pulling an entire Java interpreter into pcscd. What you<br>
> could do is a bridge that talks to a Java program running in another<br>
> process, but I think that's going to be more troublesome than it's<br>
> worth.<br>
><br>
> jPAM in fact does not do this; what it does is let Java applications</p>
<p dir="ltr">So I may have been wrong about jPAM, it was a 2 second google search. But pulling the python interpreter or JVM into pcscd is logically not different. In fact I already have a stub that does all of what I described. Its pretty simple.</p>
<p dir="ltr">See: <a href="http://www.inonit.com/cygwin/jni/invocationApi/c.html">http://www.inonit.com/cygwin/jni/invocationApi/c.html</a></p>
<p dir="ltr">> call PAM, not the other way around. pam-python _does_ let you write PAM<br>
> modules in Python; it does this by spinning up a Python interpreter in<br>
> the PAM module. That works because Python is designed to be embedded in<br>
> another program in this way and because it will be shut down and<br>
> unloaded when the module is removed, which happens no later than when<br>
> the application calls pam_end().</p>
<p dir="ltr">So JVM is designed to be embedded as well, see above. Additionally everything goes away on the so unload.</p>
<p dir="ltr">><br>
> -- Jeff<br>
><br>
><br>
> _______________________________________________<br>
> Pcsclite-muscle mailing list<br>
> <a href="mailto:Pcsclite-muscle@lists.alioth.debian.org">Pcsclite-muscle@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pcsclite-muscle">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pcsclite-muscle</a><br>
</p>