Hosting a Web Service in a Windows Service -- dotnet web services

FrancoisViljoen
1/4/2007 10:21:00 PM

OK, if I understand correctly, the client needs to query and change state of
the service via an open communications layer.

I would develop the web service as a normal .NEt IIS hosted web service that
merely queries the service via some mechanism (remoting over TCP comes to
mind here)

I hope this helps.

[quoted text, click to view]

Tejasvi Hegde
2/2/2007 10:42:04 AM

[quoted text, click to view]

Web Services Enhancements (WSE) should solve your problem.

Refer:
http://msdn2.microsoft.com/en-us/library/aa529311.aspx

Rgds,
Tejasvi

BizTalk Utilities - Frustration free BizTalk Adapters

Tim
2/20/2007 5:30:47 PM

Assuming your server is .NET 2.0 application then WSE 3.0 is a possible
method you could use; as per the previous post. To elaborate you could WSE
enable your service and use the TCP transport mechanism to communicate to
your service using SOAP over the TCP protocol assuming you wanted to keep
this all in process?

Essentially within your service you can derive a class from SoapService and
register it with the SOAPReceivers collection specifying the endpoint
reference of your server host ip and a desired port to listen on.

Within your client application you can derive from SoapClient and
communicate via an endpoint reference to the ip/port that your service is
listening on.

There are samples that show this within the WSE 3.0 SDK download.

Rgds,
Tim.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet web services

dotnet web services : Hosting a Web Service in a Windows Service