Figure 4-76 IBM Interface Tool for Java: inter-process solution candidate: .NET remoting
Figure4-77 illustrates a solution candidate that uses DCOM as the inter-process
communication mechanism. This solution model is simpler than that illustrated in
Figure 4-76 because we do not need to build .NET remoting proxies or stubs. It
also has the benefit of not requiring a .NET CLR to be loaded into the client’s
JVM process. It delivers complete separation between Java and .NET.
Figure 4-77 IBM Interface Tool for Java: inter-process solution candidate: DCOM
So far, each of these solution candidates has ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.