Phil, The http can be configured with either the binary and the text formatter - the first one, obviously, is much faster.
The real reason why http channel + binary formatter is better than the tcp channel (which itself is rarely used with any other formatter) is that messages begin with POST /<some_url_here> <more headers...> Followed by binary data. Although this data is most certainly not HTML, it is a quite valid http transaction so most firewalls pass it through without a glitch. (Same goes for http response) Re: bidirectional communication - i.e. calling the client from the server, or using events on server-based objects - there's a long list of "don't do it!" type arguments. This has been discussed a lot on this list - look for it in the archives - and elsewhere on the web. Google is your friend :) Kamen Lilov Delera Systems http://www.delera.com -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil D Sent: Monday, August 29, 2005 8:09 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Reasons to use HTTP remoting I've heard http remoting described as "firewall friendly" because it's text-based, presumably because there are firewalls (or filters) that can be configured based on text in messages. I suspect that being able to see the data might also give network administrators some sense of security. Phil Wilson [del] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
