Ralph Shnelvar wrote:
I want to use Rails to
(1) Download an executable.
This part is trivial.
(2) Interact with a client to select a directory on the client side
This happens automatically depending on what web browser the client
(3) do directory browsing and selecting
Thank goodness this is not possible through standard web technologies.
(4) create an xml file of parameters, and write the xml file somewhere
or pass it to the executable.
Much effort has been put into web browser security to prevent this exact
That is unless you crack open the shell of security & privacy with
something like ActiveX or Adobe Flash. This is also why both of those
have been a "secret weapon" of malicious hackers for years.
Basically, I'd like to use Rails to create a front-end for my user and,
of course, interact with my Rails server.
Is this doable or am I better off having my client download a
stand-alone Ruby application? If a standalone Ruby application is
better, can someone recommend a GUI that you might suggest?
This is rather difficult to answer without knowing what that executable
program actually needs to do. How complicated will the GUI need to be?
What are the security & privacy concerns associated with what you're
trying to accomplish?
I for one would be extremely reluctant to install your application on my
system (I wouldn't have any way to do so anyway given I don't run
If your site is intended to be used by known clients, that already trust
you, then there are certainly some options. If your site is even
remotely public, and you expect clients to "just trust you," then your
approach is not plausible. You cannot expect, or force, people to trust
you. Thankfully trust is in control of the client (unless, of course, if
the client's system security has been compromised).