@emir.subasic
If your question is related to your other post here, then as @Zhenya Kovalyov replied on that thread, the behavior you described is absolutely not expected. In fact it makes no sense to me at all.
To answer your question on this thread, the communication between Eikon .NET API and Eikon processes is over named pipes. And, as @Zhenya Kovalyov said, COM dlls are involved.

@emir.subasic as far as I know, it uses an internal COM API under the hood.

Thanks for confirming.