S
Steven Blair
I need to write a service and I am unsure which particular type I should
be using:
Key requirements:
1. Service must be able to run 24/7
2. Persist certain data items (logging to disk or DB is not permitted)
So after reading about, I see the following options available to me:
1. Windows Service
2. ASP.NET Web Service under II6
3. WCF Web Service II6/7
4. WCP Web Service under WAS
The Windows Service in my opinion seems the best option regarding
persistent data, but it's a lot more complicated to write certain
features you kinda get free with Web Services.
The Recycling is the really the big problem under IIS since I need to
keep values. Turning recycling off is not good enough either (touching
files etc cause a recycle)
Does WCF allow you to persist data, or does WAS allow this?
I don't mind learning new technology, so a pointer in the right
direction would be appreciated.
A final note, it doesn't need to be a HTTP interface if there are other
options. Only reason thats being used is II6 enforces this but we took
the trade off for the lovely features of II6 over writing a custom
Windows Service.
Thanks in advance.
Steven
be using:
Key requirements:
1. Service must be able to run 24/7
2. Persist certain data items (logging to disk or DB is not permitted)
So after reading about, I see the following options available to me:
1. Windows Service
2. ASP.NET Web Service under II6
3. WCF Web Service II6/7
4. WCP Web Service under WAS
The Windows Service in my opinion seems the best option regarding
persistent data, but it's a lot more complicated to write certain
features you kinda get free with Web Services.
The Recycling is the really the big problem under IIS since I need to
keep values. Turning recycling off is not good enough either (touching
files etc cause a recycle)
Does WCF allow you to persist data, or does WAS allow this?
I don't mind learning new technology, so a pointer in the right
direction would be appreciated.
A final note, it doesn't need to be a HTTP interface if there are other
options. Only reason thats being used is II6 enforces this but we took
the trade off for the lovely features of II6 over writing a custom
Windows Service.
Thanks in advance.
Steven