🚀 go-pugleaf

The DLL purpose is to allow the application (BCB or VC++) to create one or 
more instances of a syslog thread.  The reason, my company seems to have 
various logging systems, bespoke for each development, and it would seem a 
good idea to standardise it using a known standard.

I've made some assumptions with the design of the DLL, and one of those is 
that the TIdSysLog can be handled in a TThread, thus not blocking the main 
application (it appeared to work in a test application).

The DLL has three functions:

// create/start thread for handling TIdSysLog, a thread Q
IMPORT_EXPORT unsigned long   __stdcall TheSysLogTaskStart ( const char * 
In_ProcessName,
                                                             const unsigned 
long In_ProcessID,
                                                             const char * 
In_ServerAddress,
                                                             const unsigned 
long In_ServerPort,
                                                             void** 
Out_ClientHandle );

// terminate/destroy thread for handling TIdSysLog
IMPORT_EXPORT unsigned long   __stdcall TheSysLogTaskStop ( void** 
In_ClientHandle );

// create and add a syslog message to the Thread's input Q
IMPORT_EXPORT unsigned long   __stdcall TheSysLogTaskSend ( const void** 
In_ClientHandle,
                                                            const unsigned 
long In_Severity,
                                                            const unsigned 
long In_Facility,
                                                            const char * 
In_Message );

I must admit, I don't know what to put into DllEntryPoint() function, or 
DllMain(..).  I've read the help system and can't make much sense of it 
(still much to learn about DLLs I suspect).

Paul


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4427065d$3@newsgroups.borland.com...
> What exactly is your DLL code actually doing, particularly in its
> DllEntryPoint() function?
>
> Gambit