T
Tom
Hi newsgroup,
I have the following situation:
There is a webapplication, written in ASP.NET (C#), which should allow
several users to control some hardware devices over an intranet. The
devices are all connected onto the same machine, than IIS is running.
Because of several users could use the same device, I will have to
write some kind of queue - which should be not a problem.
This alone would be no problem, because I can handle this through the
..NET-framework classes.
But there are several devices, which should be controlled by
time-parameters AND also through the user queue - so I have to write
code which takes control about the devices within the same process.
Does anybody know a way, how to write a windows service application in
C#, which could be controlled by a web application, written in ASP.NET
(C#) ?
This would be a good solution, I guess. I then could place the queue
and the device controllers into the local service app and only start
new "jobs" and request the current status out of the ASP.NET app.
I know there could be a way using a database behind, but this will be
to slow - we are fighting for each millisecond.
I would be glad, if anyone has any further ideas how I can solve my
problem.
THX
Tom
I have the following situation:
There is a webapplication, written in ASP.NET (C#), which should allow
several users to control some hardware devices over an intranet. The
devices are all connected onto the same machine, than IIS is running.
Because of several users could use the same device, I will have to
write some kind of queue - which should be not a problem.
This alone would be no problem, because I can handle this through the
..NET-framework classes.
But there are several devices, which should be controlled by
time-parameters AND also through the user queue - so I have to write
code which takes control about the devices within the same process.
Does anybody know a way, how to write a windows service application in
C#, which could be controlled by a web application, written in ASP.NET
(C#) ?
This would be a good solution, I guess. I then could place the queue
and the device controllers into the local service app and only start
new "jobs" and request the current status out of the ASP.NET app.
I know there could be a way using a database behind, but this will be
to slow - we are fighting for each millisecond.
I would be glad, if anyone has any further ideas how I can solve my
problem.
THX
Tom