Seems to be some confusion, so I'll see if I can clear it up. I have 2 AppDomains that I did not create, and they make remote calls via HTTP to a server on the web. Seems there is an issue with making remote calls from 2 AppDomains, and the second one always fails.
I tried to make cross-domain calls to see if I could fix it (i.e. get the first AppDomain to create the remote calls on behalf of the second AppDomain), but I do not know if that's even going to work. I would need to get a reference to the RemoteFactory in the first AppDomain from the second AppDomain, and then use that to make the remote calls out to the web server, and that returns a reference to an instance of a class on the web server, which I then call methods on. Because I have no references to the AppDomains, cross-domain remoting with ICP might work to give me access to the remote class - but will calling that class work correctly to get references to remote instances as well? Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Mark Hurd Sent: Saturday, 14 October 2006 13:13 To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Get an AppDomain you didn't create On 10/14/06, Dean Cleaver <[EMAIL PROTECTED]> wrote: > I'm actually using HTTP, because this application needs to work from > all over the world, and http traffic is very rarely blocked. I figured > my chances of sending out an HTTP request from a hotels broadband > system was higher than trying to connect to a different port using TCP. I meant to try using IPC for your workaround remoting between AppDomains. Regards, Mark Hurd, B.Sc.(Ma.)(Hons.) =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
