1

Topic: Re: to Tighten win32 dll a plug-in in Java x64 process

Hello, Tyomchik, you wrote: Those> Are    with the interface of the extension of a C ++ dll. There are extensions (dll) which  time-series and cause callback. Those> It would be desirable to give this api under , and application will be on Java. Those> Idea what probably to write winelib - substitute process which would load dll and pulled at it methods, gave to it callback. That java - process it is reserved spawn-l this substitute and sent it commands, gave the data on an input and took away results through memory-mapped file. Over-engineering turns out. Whether there are examples of ready decisions? Whether it is possible to make is easier somehow? JNI + https://github.com/taviso/loadlibrary

2

Re: Re: to Tighten win32 dll a plug-in in Java x64 process

In my opinion most made variant will be - to untie this DLL from , to make its cross-platform (what for to it ?), and communication with Java to organize on a network, for example through the REST-interface or WebSockets. Or communication to make through stdin/stdout if such primitive interface suffices. With JNI there will be a problem that  64-bit, and application 32-bit. It is necessary either there or there.

3

Re: Re: to Tighten win32 dll a plug-in in Java x64 process

Hello, vsb, you wrote: vsb> In my opinion most made variant will be - to untie this DLL from , to make its cross-platform (what for to it ?), and communication with Java to organize on a network, for example through the REST-interface or WebSockets. Or communication to make through stdin/stdout if such primitive interface suffices. Is better the problem that  64-bit, and application 32-bit will rewrite on java vsb> With JNI. It is necessary either there or there. It not only in  such problem Then something of type vm in vm https://github.com/ianopolous/JPC