 | 1 | initial version |
UPDATE Just finished with tests of my app and my requested feature. So now gonna share info. If somebody faced with same kind of problem - here is how I managed to meet my needs. I have written simple console app in C++, which loads EPAN Framework lib into it's memory space (it loads my custom API Dll, and my Dll preloads actual EPAN Dlls after all), and with this approach I actually got an isolated EPAN infrastructure, and now, by using it, I'm able to dissect some packets completely independently with no affect on my main stream. Also, the C++ app is used just as an child process of my main app, and all communication (IPC) is implemented through Win Named Pipes + JSON serialization\deserialization. I don't rly have many API calls (about 15 for now), so it is decent for me to use this approach.
Maybe there is some better\modern approaches, but since I'm not that pro in C/C++ I did my best, and share here :) Cheers.
| | 2 | No.2 Revision |
UPDATE
Just finished with tests of my app and my requested feature.
So now gonna share info. If somebody faced with same kind of problem - here is how I managed to meet my needs.
needs.
I have written simple console app in C++, which loads EPAN Framework lib into it's memory space (it loads my custom API Dll, and my Dll preloads actual EPAN Dlls after all), and with this approach I actually got an isolated EPAN infrastructure, and now, by using it, I'm able to dissect some packets completely independently with no affect on my main stream.
stream.
Also, the C++ app is used just as an child process of my main app, and all communication (IPC) is implemented through Win Named Pipes + JSON serialization\deserialization. I don't rly have many API calls (about 15 for now), so it is decent for me to use this approach.
Maybe there is some better\modern approaches, but since I'm not that pro in C/C++ I did my best, and share here :) Cheers.
| | 3 | No.3 Revision |
UPDATE
Just finished with tests of my app and my requestedI have written simple console app in C++, which loads EPAN Framework lib into it's memory space (it loads my custom API Dll, and my Dll preloads actual EPAN Dlls after all), and with this approach I actually got an isolated EPAN infrastructure, and now, by using it, I'm able to dissect some packets completely independently with no affect on my main stream.
Also, the C++ app is used just as an child process of my main app, and all communication (IPC) is implemented through Win Named Pipes + JSON serialization\deserialization. I don't rly have many API calls (about 15 for now), so it is decent for me to use this approach.
Maybe there is some better\modern approaches, but since I'm not that pro in C/C++ I did my best, and share here :) Cheers.
| | 4 | No.4 Revision |
UPDATE
Just finished with tests of my app and my requested feature. So now gonna share some info. If somebody faced with same kind of problem - here is how I managed to meet my needs.
I have written simple console app in C++, which loads EPAN Framework lib into it's memory space (it loads my custom API Dll, and my Dll preloads actual EPAN Dlls after all), and with this approach I actually got an isolated EPAN infrastructure, and now, by using it, I'm able to dissect some packets completely independently with no affect on my main stream.
Also, the C++ app is used just as an child process of my main app, and all communication (IPC) is implemented through Win Named Pipes + JSON serialization\deserialization. I don't rly have many API calls (about 15 for now), so it is decent for me to use this approach.
Maybe there is are some better\modern approaches, but since I'm not that pro in C/C++ I did my best, and share here :)
Cheers.
Cheers :)
