multiple clients - single server application, each as separate processes

[Selçuk Cihan]

On Sat, Feb 16, 2008 at 6:03 PM, Lukasz Michalski <lm at zork.pl> wrote:
>  wxSOCKET_BLOCK is meaningless in child threads - it will not block GUI,
>  because there is no GUI and event loop there, but it has to be used to
>  prevent wxSocket calls from spinning CPU to 100%.


hi, is the following scenario possible? two threads share a
wxsocketbase object and one always reads the other always writes.
there is no synchronization effort.