[Mono-list] Remoting and Apache at the same time (and port)?

Carlos Ble carlosble at shidix.com
Fri Jan 20 10:01:06 EST 2006

Hi Andres, If you try to run your Remoting server at port 80 when Apache
is already running you will get an exception:
System.Net.Sockets.SocketException: Address already in use
To cross most firewalls you can try to use other ports like 443, 3128,
Other option could be to place a web service that connects to the
Remoting Server like a client. 


El vie, 20-01-2006 a las 14:39 +0100, "Andrés G. Aragoneses" escribió:
> I am beginning to dive inside Remoting and I have read the following
> sentence in a .NET book:
> > Web services are requested much like a web page over an HTTP channel. This allows web-service requests to cross most firewalls. Of course, the same is possible with Remoting, as long as you configure your component accordingly.
> However, this leads me to a new doubt: if I want to deploy a
> Remoting-powered solution that bypasses most firewalls, I have to
> install my application in port 80, and use and HttpChannel (although
> this last requisite is not necessary I think), right? But does this
> require that my application must monopolize the http port? I mean: can I
> have a server with Apache running and with my Remoting application
> running in port 80 at the same time? If this is possible, I suppose that
> I must use some kind of redirection from Apache invokations that request
> the specific URI of my remote singleton object, like mod_mono does with
> XSP (AFAIK), so: is this possible right now or there should be a new
> implementation of a special module for Apache, similar to mod_mono? BTW:
> is this possible with IIS?
> Any comments would be really appreciated.
> 	Andrés	[ knocte ]

More information about the Mono-list mailing list