Hi Friends,
I am facing a very wierd situation and dont know how to apply .net design
pattern to resolve the same. My application is a distrubuted setup where
clients (from different machines) call a web service. The central web
service should be a daemonized process (like winnt services) and perform
other processing while accepting client requests. If I use a web service as
my central processing server then everytime a new client connects to it, IIS
will create a new process for the web service (I dont think I can use
singleton pattern here since processes will be different). If I create a
windows service then I lose soap interface (well ya I could use sockets but
automatic method invocation like in asp.net webservice is highly
desireable). I am sure this must be a common arch problem. Any hints on
this?
Thanks
Ashish

Hi Ashish,

Thanks for using the Microsoft Developer Newsgroups. I have sent your
issue on to one of our support teams to get an answer to your question. I
will reply with their response as soon as I receive it.

Thanks for your patience!

Brett Keown
Microsoft Support
brettke (AT) online (DOT) microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Brett... waiting to hear from your side ...
Ashish

"Brett Keown [MSFT]" <brettke (AT) online (DOT) microsoft.com> wrote

Hi Ashish,

I am still working on this. It shouldn't be too much longer. Thanks!

Brett Keown
Microsoft Developer Support
brettke (AT) nospam (DOT) microsoft.com

To email me directly, please remove the "nospam" from my email address.

This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.

Just to keep this thread alive... :-)
Ashish

"Brett Keown [MSFT]" <brettke (AT) online (DOT) microsoft.com> wrote

rights reserved.

A service instance will be created for each call.

Does you need to hold the connection for each client?
Does you need to share state across the clients?

David
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

Hi David,
Thanks for your reply. As I said I want to design a daemonized service which
could be a windows service. I donot intend to hold connections for clients.
WS would act as a medium of information exchange, treat it as a replacement
of standard practice of using raw sockets from win services. Daemon will not
start / die after each requests, rather requests can be treated as
interrupts. So far from my knowledge I can host remoting objects with server
activated singleton configuration from win service and forward my calls from
asp.net WS to these remoting objects. I just donot know if this is a hack or
a proper way to do it.
Thanks
Ashish

"David Qiu" <davidqiuonline (AT) microsoft (DOT) com> wrote

Hi Ashish,
Looks like hosting singleton remoteing objects in IIS will achieve what you
want.

David

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ashish,
You have two solutions:
- Singleton remoteing object in IIS. You take the advantage of IIS built-in
security.
- Singleton remoteing object in Windows services over HTTP using SOAP

You need to call it first to create the object.

Thanks,
David
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights.