P
Passiday
Hello,
We have this web application (it's developed in C#, but that really
does not matter), and part of it's functionality is to print some data
on a specific kind of printer that's attached to the user's PC. The
printer will print if a file to print is placed in specific configured
folder in the PC's local file system. So the web app that resides in
the browser, pretty ignorant about the PC where it is running on,
needs to trigger a local process that will result in the file created
in the needed place.
Right now we go with rather heavy solution - a local webserver is
installed and the web app passes the data to local URL, and the tiny
script does it's thing - collects the data and creates the file in the
needed place.
I am now wondering if we could set it up in more elegant way:
1) Have a local C# app triggering regularly far web server "is there
anything for printing".
- pros: seems simple to implement
- cons: regular far webserver triggering sounds like bad architecture.
Also delays could be a problem.
2) Have a local C# app that acts as simple http server
- pros: sounds like the most direct way to pass down info to local app
from the browser
- cons: potential security problems? Could be complex to develop?
Maybe there is some other smart idea how a local process can be
triggered from a web app?
Passiday
We have this web application (it's developed in C#, but that really
does not matter), and part of it's functionality is to print some data
on a specific kind of printer that's attached to the user's PC. The
printer will print if a file to print is placed in specific configured
folder in the PC's local file system. So the web app that resides in
the browser, pretty ignorant about the PC where it is running on,
needs to trigger a local process that will result in the file created
in the needed place.
Right now we go with rather heavy solution - a local webserver is
installed and the web app passes the data to local URL, and the tiny
script does it's thing - collects the data and creates the file in the
needed place.
I am now wondering if we could set it up in more elegant way:
1) Have a local C# app triggering regularly far web server "is there
anything for printing".
- pros: seems simple to implement
- cons: regular far webserver triggering sounds like bad architecture.
Also delays could be a problem.
2) Have a local C# app that acts as simple http server
- pros: sounds like the most direct way to pass down info to local app
from the browser
- cons: potential security problems? Could be complex to develop?
Maybe there is some other smart idea how a local process can be
triggered from a web app?
Passiday