🚀 go-pugleaf

i managed to solve the problem with opening many instances of the server 
application. actually it is
something that happens in order to have a pool of remote datamodules 
available for the clients. the instancing
option in tools->options->atl can be set to multi in order to allow one 
remote datamodule to serve many clients instead of
opening one remote datamodule instance per client request. to be honest i 
dont pretty much understand the reason for having
many remote datams running,i think one can do the job and can save  server 
resources. but the other problem still remains.

if the server is not open and a client requests ,the server opens 
automatically. how can we fix this issue?
thanks


"abc" <abc@dd.com> wrote in message news:46822274@newsgroups.borland.com...
> hello im using borland c++ builder 2006 for creating a multitier datasnap 
> based application.
> the application runs normally but i have encountered an issue which i dont 
> know if its normal or not.
>
> in order to replicate the issue just follow the steps:
> 1.create a simple datasnap server -client applications
> 2. open the scksrv.exe in the server side.
> 3. run the client without running the server
> at that point you will see that the scksrv.exe opens the server program 
> without asking.
> clients can start the servers program this way,is there any way that we 
> can avoid it?ofc
> one way is to close the scksrv.exe,but is there any option that can stop 
> this from happening?
>
> moreover i have observed an even stranger behaviour...
> if the client program and the server program are both open, the client 
> terminates unenxpected
> for some reason(e.g. throw an exception and close) , and then reopen the 
> client, the scksrv.exe opens a new instance
> of the server program...(so in the server maschine there will be 2 
> instances of the same server program...)
> any ideas on this issue?
>
> i havent included any code because there is no need to, just create a 
> simple datasnap server-client and observe their
> behaviour.
> thank you for your time
>