remoting - What is the underlying mechanism used to communicate between .Net AppDomains in the same process? -
I would realize a rational knee-jerk reaction "You're stupid remoting! Read MSDN docs." I can find out about every scrap of information. Net remoting is in the context of inter-process communication: sockets, shared memory, pipe ... classics when it comes to IPC, but an appdomain is not really a process. However, AppDomains enjoy the most benefits of being one. From an academic perspective, OS IPCs are heavier than communication between old institutions, which remain in the same process. Is there a special apparmon pipe that uses the communication process to cross an appledom limit within the same process? I doubt it. I would be surprised if MS has changed the basic principles of process alienation in the Windows kernel to adjust app docs.
In this case there is no need for a faster way to enterprosession communication, as the appdomain is in the same process And CLR has all those and full addresses. This is actually a few markers in the call stack as well as fluctuations provided by the appdomain for the purposes of security and exception handling.
Comments
Post a Comment