Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread External module calling back to the server
Tue, Jun 17 2008 12:01 AMPermanent Link

Oliver Bock
I am trying to plan moving from DBISAM to ElevateDB, and it seems that
v2 will soon have everything I need.

My goal is to continue to have the bulk of my code in a single
executable, so I can use the same executable both as the client and as
the server, and via a local database when executing for a single user.

Here is my scheme.  The multi-role executable is called oliver.exe and
the DLL is called stub.dll.

- When oliver.exe starts as a server, it:
  a. Calls oliver.dll to provide a pointer to a function in oliver.exe.
  b. Registers stub.dll with ElevateDB as a an external module.
  c. Starts TEDBEngine in server mode.

- When oliver.exe running as a client executes an external stored
  procedure, ElevateDB invokes stub.dll, which uses the pointer it was
  provided and calls back to the server process.  The server process
  perhaps creates a session and does some work and the returns.

Is this likely to work?


  Oliver
Tue, Jun 17 2008 9:19 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Oliver,

<< Is this likely to work? >>

I don't see any problem with it - it's all within the same process boundary,
so it should be allowed under Vista and the newer OS's.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image