Re:Oracle to issue huge security patch addressing 36 Java vu...
by skybrian on Tuesday January 14, 2014 @05:38PM
(#7060302)
Why not an HTTP server running on localhost that provides these things?
Re:Oracle to issue huge security patch addressing 36 Java vu...
by y0ghur7_xxx on Tuesday January 14, 2014 @06:09PM
(#7060455)
Yes, we thought of that too, but the installation of the server on every client was a lot more work than writing an applet. But it was a valid alternative if the clients using the app where few.
Re:Oracle to issue huge security patch addressing 36 Java vu...
by Joister on Tuesday January 14, 2014 @09:36AM
(#7057245)
Out of curiousity, why did it have to run in the browser?
Re:Oracle to issue huge security patch addressing 36 Java vu...
by y0ghur7_xxx on Tuesday January 14, 2014 @09:40AM
(#7057268)
Why not? - "we did not want to write a desktop app just for these features"
- direct access to printer: the user wanted to print on a specific tray of the printer, without selecting it every time. JS only implements window.print() with no fine grained printer control.
- serial/parallel/usb access: access to a POS for card processing, and we needed to write some data on a smartcard.
- plain TCP connections
- read/write files on the local filesystem.
I understand that all these features require more control of the underlying hardware and need to be somehow secured, but we did not want to write a desktop app just for these features, and applets gave us the means to implement what the user needed. Once JS can do that, applets can die a quick dead.