B
Bob Altman
This is a follow-on to my previous post. It occurs to me that I asked the
wrong question.
Here's what I'm really trying to accomplish: My application is a real-time
airplane and avionics simulation. My application includes a .Net singleton,
exposed via remoting, that allows clients to do things like starting,
stopping, and resetting the simulation. We also include a web service that
allows remote clients (on Linux boxes) to control the simulation.
Running IIS to expose our web service to the world poses several challenges
for us. First of all, we need to install it and configure it correctly on
each computer that runs our app. In addition, it's probably serious
overkill for what we're trying to accomplish.
We want to simplify deployment and configuration of our application. We
also want to eliminate as much extraneous stuff from Windows as we can to
improve our real-time performance.
What I'm really looking for is a web server that I can easily integrate with
my existing web service code. Maybe IIS7 can be trimmed down to be about as
good a solution as I can get (in which case I'm probably posting this to the
wrong newsgroup). But maybe I can do better by hosting my web service in my
own application.
I looked at the Cassini example and the ApplicationHost class. It's not at
all obvious to me how to wire things up with ApplicationHost so that my web
service works. In any event, it looks like a *lot* of work get get it
working.
I could use the ServiceHost class, but that presents a problem for me
because I need to run my app on some Windows 2000 computers (in addition to
a bunch of Windows XP computers). I'd be willing to go down this path if
using ServiceHost gets me a lighter weight, more easily configured solution
than using IIS. (I'd install this on the Windows XP hosts, and install IIS
on the Windows 2000 hosts.)
Any thoughts or suggestions would be greatly appreciated!
- Bob
wrong question.
Here's what I'm really trying to accomplish: My application is a real-time
airplane and avionics simulation. My application includes a .Net singleton,
exposed via remoting, that allows clients to do things like starting,
stopping, and resetting the simulation. We also include a web service that
allows remote clients (on Linux boxes) to control the simulation.
Running IIS to expose our web service to the world poses several challenges
for us. First of all, we need to install it and configure it correctly on
each computer that runs our app. In addition, it's probably serious
overkill for what we're trying to accomplish.
We want to simplify deployment and configuration of our application. We
also want to eliminate as much extraneous stuff from Windows as we can to
improve our real-time performance.
What I'm really looking for is a web server that I can easily integrate with
my existing web service code. Maybe IIS7 can be trimmed down to be about as
good a solution as I can get (in which case I'm probably posting this to the
wrong newsgroup). But maybe I can do better by hosting my web service in my
own application.
I looked at the Cassini example and the ApplicationHost class. It's not at
all obvious to me how to wire things up with ApplicationHost so that my web
service works. In any event, it looks like a *lot* of work get get it
working.
I could use the ServiceHost class, but that presents a problem for me
because I need to run my app on some Windows 2000 computers (in addition to
a bunch of Windows XP computers). I'd be willing to go down this path if
using ServiceHost gets me a lighter weight, more easily configured solution
than using IIS. (I'd install this on the Windows XP hosts, and install IIS
on the Windows 2000 hosts.)
Any thoughts or suggestions would be greatly appreciated!
- Bob