dilettante
MIS
This may be old-hat and routine. It may be exotic. In any case I can't seem to locate a lot on the topic (MSDN searches, Google like a madman) which may actually be an answer to my question by itself.
I realize that DCOM is implemented on top of RPC. My question is whether or not it is possible to have code on one system invoke a library written in VB6 over RPC itself.
I have a situation where a foreign platform has an implementation of Microsoft's RPC (that is, Microsoft's version of DCE RPC over TCP/IP) that the vendor calls WinRPC. At this point I only need to have that platform be the RPC "client" to a Windows "server" even though they seem to support symmetry.
They have their own version of IDL and an IDL compiler, as well as an endpoint mapper service, locater, etc. The concepts they outline (client and server stubs, etc.) all seem to truly match those of Microsoft's RPC.
What I want to do is something along the lines of building a library using Implements: stub out my classes, compile the DLL, use OLE View to pull the IDL out of the DLL, edit the IDL, compile with MIDL, etc. Then build the real DLL based on the generated type library, and of course generate RPC stubs via MIDL, etc.
The REAL question then is: When I'm done will I have something this "WinRPC" can talk to? In other words is this something that VB can create with all these gyrations or at the end of the day am I still screwed? Will I end up having to build this as a standard DLL in C?
If so, does anyone have links to useful information or even a book title/author (preferably something still in print)?
Thanks in advance.
I realize that DCOM is implemented on top of RPC. My question is whether or not it is possible to have code on one system invoke a library written in VB6 over RPC itself.
I have a situation where a foreign platform has an implementation of Microsoft's RPC (that is, Microsoft's version of DCE RPC over TCP/IP) that the vendor calls WinRPC. At this point I only need to have that platform be the RPC "client" to a Windows "server" even though they seem to support symmetry.
They have their own version of IDL and an IDL compiler, as well as an endpoint mapper service, locater, etc. The concepts they outline (client and server stubs, etc.) all seem to truly match those of Microsoft's RPC.
What I want to do is something along the lines of building a library using Implements: stub out my classes, compile the DLL, use OLE View to pull the IDL out of the DLL, edit the IDL, compile with MIDL, etc. Then build the real DLL based on the generated type library, and of course generate RPC stubs via MIDL, etc.
The REAL question then is: When I'm done will I have something this "WinRPC" can talk to? In other words is this something that VB can create with all these gyrations or at the end of the day am I still screwed? Will I end up having to build this as a standard DLL in C?
If so, does anyone have links to useful information or even a book title/author (preferably something still in print)?
Thanks in advance.
