Hosting a webservice in a windows service WSE 3.0

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

markoueis@hotmail.com - 20 Apr 2006 19:44 GMT

I'm aware that i can host an "asmx" based webservice in a windows
service with WSE 3.0. However, i want more than that. Not just do i
want to host the webservice in my windows service, but i also want my
main windows service AppDomain to handle the webservice requests
itself. Is this possible? Are the webservice and windows service under
different app domains? Do I have to serialize the request from the
webservice to the windows service? If so, is there any fast interdomain
communication i can use?

What are my options?

Basically all i want to do is have clients accross the internet send
information to my Windows Service as fast as possible and with the
least ammount of processing (serializing, ports etc.). What's the best
way to go?

Thanks

Reply to this Message

Pablo Cibraro - 21 Apr 2006 14:47 GMT

Hi,

The WSE code that listens for incomming connections runs by default in the
same AppDomain as the host.
WSE offers different transports to expose a asmx service, such as TCP,
HTTP.SYS, MSMQ, and others (You can also build your own custom transport).

In your case, if you are planning to host a asmx on a service, I think the
HTTP.SYS is the best option. I recommend you to take a look this article
from Aaron Skonnard

http://pluralsight.com/blogs/aaron/archive/2005/10/14/15571.aspx

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

> I'm aware that i can host an "asmx" based webservice in a windows
> service with WSE 3.0. However, i want more than that. Not just do i
[quoted text clipped - 13 lines]
>
> Thanks

Reply to this Message

markoueis@hotmail.com - 21 Apr 2006 16:58 GMT

I'm taking a look at Http.sys. I'm still not sure how it works but i
can read up on that. For now, permit me to make the question a little
bit tougher. On top of everything I mentionned in the initial post, I
would also like to get the information from the clients to my windows
service , THROUGH PORT 80 (while IIS is runing). However i don't want
IIS to handle anything, just let my windows service do all the work. I
kind of want IIS to be a pass through (or something like that). The
point is, i don't want the users of the software to have to open
another port on their firewalls. Port 80 should be enough.

Thanks

> Hi,
>
[quoted text clipped - 30 lines]
> >
> > Thanks

Reply to this Message

Rate this thread:

Hosting a webservice in a windows service WSE 3.0

Free Magazines