"B. K. Oxley (binkley)" wrote:
>
> From: "Brian Ingerson" <[EMAIL PROTECTED]>
>
> > I had an idea for Inline::Java. Let's say that you had an Inline
> wrapper
> > class inside a Perl module. You should be able to make a distribution
> > (easy with the new Inline 0.40 features) and distribute the module to
> > various people. Then you could run a server script on one machine and
> > have the others use your Inline::Java based module remotely:
>
> Two comments:
>
> 1. This scares the hell out of me for security. Suddenly, Java's
> sandbox won't catch remote code (if I understand your example), and will
> let it run with the priveleges of local code. Very bad for the guys in
> white hats.
Dunno. What's the difference between this and what Java.pm does? I was
more interested in getting Patrick and Mark talking than anything.
>
> 2. Won't the performance bite? Would the module be compiled locally,
> and run from there afterwards, a kind of cache, or would it need to
> refetch the compiled code each time from the server?
I would expect poor performance from everything except Patrick's JNI
stuff. But to me, it's all about adding more options. You can always
address performance afterwards.
Cheers, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
