Martin, thanks for testing. the calling exe and the called exe server each has their own address space so that a pointer cannot be passed. Sometime it worked because com system copy all relevant data in additon to the parameters and obvious this is not very efficient. BSTR are objects accessed by pointers so that I guess they are also marshaled by copying.
a pro for exe server is that you can mix 32-bit and 64-bit programs. Птн, 15 Окт 2010, Martin Pelletier писал(а): > I only need J for file management in this project, it's a workhorse > that gets its commands from C#. So I don't need WD. thought the more > stable iterations of the project could use JDLLServer for cleanliness, > and I still look forward to that. > > I find it odd that JEXEServer would be a wrapper to JDLLServer and yet > behave differently (SetB and GetB), or worse, obfuscate a JDLLServer > function (SetM and GetM) by saying it's not supported. But this would > not be my first surprise in this great software adventure. > > Martin Pelletier > > On 2010-10-14 20:24, Alexander Rufon wrote: > [---=| TOFU protection by t-prot: 3 lines snipped |=---] -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
