As you can see there are two methods enableMultiProcessMode and markAsForkedChild used there. Those methods no longer exist on 3.6.1, does that mean in Win32 there's no more fork, or it is handled differently?.
Those methods no longer exist on 3.6.1, does that mean in Win32 there's no more fork, or it is handled differently?.
The fork mechanism for Windows was more a quick hack than a well-designed feature, so the new approach of a threaded SCP class is now the preferred way of handling multiple associations at a time.
The command line tool "storescp" still supports the fork mechanism (on both Unix and Windows systems) but that's another story...
Ok. My app implements the handleIncomingCommand method for handling requests, should I still use this method?.
Also, in the former version I implemented a ConnectToDb method in my DcmSCP inherited constructor and disconnect in the destructor, this way I had a database connection on every association, when the association finishes the database is disconnected. With the new method where should I connect/disconnect to preserve the same mechanism (connect on assocciation) ?.
I personally never used the DcmSCPPool and DcmThreadSCP classes so far, so I could only recommend to look into the source and read the documentation (this would be the same that I would have to do).
Regarding the configuration file, you can find a sample in the "dcmnet/etc" subdirectory of the DCMTK source code package. The documentation is available in "dcmnet/asconfig.txt". This is the same configuration file that is also used by storescp and dcmrecv.