Navigation:  Programming Cookbook > Sockets Connectivity > The Socket Connection Interface >

Non-Blocking

Previous pageReturn to chapter overviewNext page

Although the blocking calls described above are probably the most common way of using Sockets in your application, they do demand that you execute multiple processes to handle them. For simple applications this can be an overly complex solution so we also provide a number of non-blocking calls as alternatives. For each of these, the call returns immediately and the actual completion of the operation is signalled by an event triggered off the Socket. Interested parties can register an interest in these events using #when:send:to:.