Serialization and remoting with dynamic appdomains
- From: dave.rafkind@xxxxxxxxx
- Date: 2 Aug 2005 12:25:21 -0700
Hello all, I am attempting something tricky with remoting and dynamic
AppDomains:
I have client A, server B, server C, and assembly X.
A, B, and C are all on seperate computers, with an identical copy of
assembly X available to each.
Client A statically references assembly X.
I would like Servers B and C to dynamically reference assembly X,
through a secondary AppDomain in each server process.
I would like Client A to access server B through remoting, passing in
an object from assembly X. Then I would like server B to process this
object (in the dynamic AppDomain), and use remoting to talk to the
corresponding dynamic AppDomain on server C, where more processing
occurs. The results are sent back from C to B and finally to A, where
the results are made visible.
So far, I have run into the problem that .NET remoting is set up per
AppDomain, so if a dynamic appdomain is created, it needs to register
its own remoting services, since the serialization code in the original
AppDomain won't know about dynamic assembly X. This means that every
corresponding appdomain pair on B and C need to set up their own
private remoting links, which seems wasteful.
Wrappers and interfaces won't help me here because they will have to
cross the serialization boundary, polluting AppDomains in the process.
How should I go about doing this?
Any help is appreciated.
.
- Follow-Ups:
- Re: Serialization and remoting with dynamic appdomains
- From: dave . rafkind
- Re: Serialization and remoting with dynamic appdomains
- Prev by Date: Re: Object Design Question
- Next by Date: How possible?
- Previous by thread: Typed datasets and DateTime using .NET remoting over differing timezones
- Next by thread: Re: Serialization and remoting with dynamic appdomains
- Index(es):
Relevant Pages
|
