I'm a complete noob when it comes to RPC and Named Pipes and anything related so forgive me first off.
I've just discovered PipeRPC here and I'm hoping maybe the author some someone 'in the know' can answer a few questions about it. (I'll need to make separate threads though, they are completely unrelated questions.)
My situation is that I am working with another developer who uses C++ and who knows what else on a joint project - I only know VB6, the other developer does not... They would like to communicate back and forth between our two different applications and want to use RPC.
Having no idea what I'm doing, I found PipeRPC and referred the other developer to the project page asking if this type of code is what I need to send/receive RPC calls with their application. I directed that developer to the PipeRPC thread here, and asked if this or similar would help me accomplish these goals. The other dev pretty much said "I dunno, but I don't think so" ...
So the other dev wrote a tiny C++ DLL for me that I can use to send RPC calls for various things to their software - however we are still trying to figure out how I can receive their messages in my VB6 software.
I also suspect that, even if I were able to receive their RPC messages in my software, it would be a moot point because VB6 being a single threaded app wouldn't it pretty much hang and not process any more code while 'listening' for the RPC messages from their software? Or is this something that could be thrown into a form timer and just check for the RPC messages every once in a while (in other words, do these RPC messages/calls/whatever just 'linger around' until the app collects them?)
I've just discovered PipeRPC here and I'm hoping maybe the author some someone 'in the know' can answer a few questions about it. (I'll need to make separate threads though, they are completely unrelated questions.)
My situation is that I am working with another developer who uses C++ and who knows what else on a joint project - I only know VB6, the other developer does not... They would like to communicate back and forth between our two different applications and want to use RPC.
Having no idea what I'm doing, I found PipeRPC and referred the other developer to the project page asking if this type of code is what I need to send/receive RPC calls with their application. I directed that developer to the PipeRPC thread here, and asked if this or similar would help me accomplish these goals. The other dev pretty much said "I dunno, but I don't think so" ...
So the other dev wrote a tiny C++ DLL for me that I can use to send RPC calls for various things to their software - however we are still trying to figure out how I can receive their messages in my VB6 software.
I also suspect that, even if I were able to receive their RPC messages in my software, it would be a moot point because VB6 being a single threaded app wouldn't it pretty much hang and not process any more code while 'listening' for the RPC messages from their software? Or is this something that could be thrown into a form timer and just check for the RPC messages every once in a while (in other words, do these RPC messages/calls/whatever just 'linger around' until the app collects them?)