DataFlex

Finalize Thread Pool on Program Exit

See more Async Examples

If your code is calling asynchronous Chilkat methods (i.e. methods having names ending with "Async"), then it's a good idea to call the FinalizeThreadPool when your program is about to exit. It's best if all asynch methods have cleanly finished prior to calling FinalizeThreadPool. If any asynchronous methods are in progress when FinalizeThreadPool is called, they will be aborted and the threads shutdown. DataFlex

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoGlob
    Boolean iSuccess

    // Asynchronous Chilkat methods are run in background threads managed
    // by a thread pool manager thread, which is also a background thread.
    // Prior to exiting, it is good practice to ensure all asynchronous methods
    // have completed or are aborted/cancelled, and that the thread pool manager
    // thread is also shutdown.  
    // 
    // The FinalizeThreadPool method should be called just before the application exits
    // to ensure all background threads, including the thread pool manager thread, are
    // cleanly shutdown.

    // This is how to do it:
    Get Create (RefClass(cComChilkatGlobal)) To hoGlob
    If (Not(IsComObjectCreated(hoGlob))) Begin
        Send CreateComObject of hoGlob
    End
    Get ComFinalizeThreadPool Of hoGlob To iSuccess


End_Procedure