B
Bob Weiner
I would like to do some file processing on files received via a web upload.
Basically, the end user will upload an excel file via ASP.Net app which will
store the file in an InQueue directory. It will then launch a separate
process which will move the file to a working directory, perform some
processing, and move the updated excel file back to a OutQueue directory
which will be available to the end user via the ASP app.
What is the best way to configure this while keeping the web app decoupled
from the processing app?
The straightforward approach would be to create a web app which launched a
console app for the second phase. Of course, it is running on a server so i
don't really need the console. Another option would be to create the
processing app as a windows service but it won't be that heavily used and I
see no point to keep the program loaded.
It seems like this is a common situation so I was wondering what the "right"
answer was?
Thanks,
bob
Basically, the end user will upload an excel file via ASP.Net app which will
store the file in an InQueue directory. It will then launch a separate
process which will move the file to a working directory, perform some
processing, and move the updated excel file back to a OutQueue directory
which will be available to the end user via the ASP app.
What is the best way to configure this while keeping the web app decoupled
from the processing app?
The straightforward approach would be to create a web app which launched a
console app for the second phase. Of course, it is running on a server so i
don't really need the console. Another option would be to create the
processing app as a windows service but it won't be that heavily used and I
see no point to keep the program loaded.
It seems like this is a common situation so I was wondering what the "right"
answer was?
Thanks,
bob