(DataFlex) Async Accept Socket Connection

Demonstrates how to get the connected client socket after accepting a connection asynchronously.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoListenSocket
    Boolean iSuccess
    Integer iMaxWaitMs
    Variant vAcceptTask
    Handle hoAcceptTask
    Handle hoConnectedClient
    String sTemp1

    // This example assumes the Chilkat Socket API to have been previously unlocked.
    // See Socket Unlock Sample for sample code.

    Get Create (RefClass(cComChilkatSocket)) To hoListenSocket
    If (Not(IsComObjectCreated(hoListenSocket))) Begin
        Send CreateComObject of hoListenSocket
    End

    // Bind to a port and listen.
    // This example will listen at port 5555 and allows for a backlog
    // of 25 pending connection requests.
    Get ComBindAndListen Of hoListenSocket 5555 25 To iSuccess
    If (iSuccess <> True) Begin
        Get ComLastErrorText Of hoListenSocket To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    // Start a background task to accept an incoming connection ...
    Move 20000 To iMaxWaitMs
    Get ComAcceptNextConnectionAsync Of hoListenSocket iMaxWaitMs To vAcceptTask
    If (IsComObject(vAcceptTask)) Begin
        Get Create (RefClass(cComChilkatTask)) To hoAcceptTask
        Set pvComObject Of hoAcceptTask To vAcceptTask
    End
    Get ComRun Of hoAcceptTask To iSuccess

    // ...
    // ...
    // ...

    // Imagine at this point the task has completed successfully,
    // and a connection was accepted.  Here's how to get the connected socket...
    Get Create (RefClass(cComChilkatSocket)) To hoConnectedClient
    If (Not(IsComObjectCreated(hoConnectedClient))) Begin
        Send CreateComObject of hoConnectedClient
    End
    Get ComLoadTaskResult Of hoConnectedClient vAcceptTask To iSuccess

    // Here's how it works:  The AcceptNextConnection method would normally
    // return a socket object when called synchronously.  When called asynchronously,
    // it cannot do so because it returns the task object.  When the async method
    // (running in a background thread) completes, the socket object that is the client
    // connection is contained within the task object.
    // 
    // This can be generalized for any case where a Chilkat method returns an object.
    // The async version of that method is such that the object returned in the background
    // thread is contained within the task object.

    // To get the result object, we create a new object instance of that type.
    // In this case, we create a socket object (connectedClient).  There is a LoadTaskResult
    // method in all Chilkat classes that can be a return value of an async method call.
    // The LoadTaskResult method transfers the returned object from the task to the caller.


End_Procedure