🚀 go-pugleaf

Hi,

I have an application that uses TServerSocket. The TServerSocket is created
dynamically, and the connect, disconnect and read methods are attached to
__published methods of a TDataModule object, at runtime.

This works fine when run interactively: I have a form with a button, whose
onclick calls a global method (startServer) which creates the TServerSocket
dynamically (maintained in a global TServerSocket*, after being created by
new
TServerSocket(NULL)), assigns the serverType (non-blocking) and the event
handlers, and opens the socket (->Open()). Once the server is thus started,
the
functionality in the OnClientRead method is available to TCP clients
connecting/communicating with the server, and all three events, namely
OnClientConnect,  OnClientDisconnect and OnClientRead write to the log file.

Currently, I am trying to convert this application into a Windows Service.
In
this case, I do not create the form with the button on it, and instead
create
only the TDataModule with the event handlers, and on service startup, call
the
global method (startServer) that sets the server listening. I can see that
the
server is listening on the specified port through netstat, once I start the
service; But apparently, none of the TServerSocket events are triggered when
a
client connects, writes to the connection or disconnects, since none of the
log file entries expected from these methods are writte to the file. From
the client end,
it is possible to establish a connection, write to it and close it; but when
an
attempt is made to read, the client hangs up, and does not return until the
service is stopped, at which time the TServerSocket->Close() is called and
the
server is stopped.

Is there any reason for VCL component events to not fire when run as a
windows
service ?

Thanks,
Naresh.