|Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder Web Server and Modules » View Thread|
|Messages 1 to 4 of 4 total|
|Calling Module DLL from a Web Server|
|Wed, Oct 19 2016 8:36 AM||Permanent Link|
I've to write a replacement for the ewbsrvr.exe for our needs. We've a custom module (derived from TEWBModule)
handling TServerRequests (no dataset/database handling).
Is there information available how to commumicate from a webserver with the module DLL when handling module rescource requests? There are exported functions in the DLL...
but I did'nt find descriptions in the Modules Manual.
|Wed, Oct 19 2016 11:14 AM||Permanent Link|
Tactical Business Corporation
If you are rewriting a server, then you will need to write all your own helper functions that you don;t even know exists in the current server, that support the dll - let alone worry about the function call to the dll.
If you are rewriting a server then you are petty much rewriting everything.
|Wed, Oct 19 2016 2:27 PM||Permanent Link|
On 10/19/2016 8:36 AM, Michael Dreher wrote:
> I've to write a replacement for the ewbsrvr.exe for our needs. We've a custom module (derived from TEWBModule)
> handling TServerRequests (no dataset/database handling).
Just to add to Walter's response - i'm curious why would you even bother
with the module if you're writing your own server ?
Just implement everything in the web server direct - everything is basic
web request/response and if you do need to support EWB TDataset then API
and JSON references are in the manual (last 2 links on this page :
|Thu, Oct 20 2016 8:40 AM||Permanent Link|
// Just to add to Walter's response - i'm curious why would you even bother
// with the module if you're writing your own server ?
// Just implement everything in the web server direct ....
My first thought was, it'll be simpler to call the module DLL for service, instead of integrating der module code in the server. The module does the database stuff, the server only knows about providing static rescources and forwarding module requests (decoupeling rules).
The more I think about what Raul wrote, it seems to be the better approach (no communication overhead, simpler implementation).
Thanks for the replies. No more answer required to the initial question.