🚀 go-pugleaf

Paul wrote:

> I'm setting the socket type to nonblocking, is this the problem, should non 
> blocking components be used in threads? 

Yes. You cannot use nonblocking in a thread as that depend on events triggered
from a message queue. There is no such queue in your thread. But you could
add such a loop I think.

> And I'm passing NULL in the 
> constructor parameter for the component, does anyone know what this is used 
> for, 

As usual the -vcl-owner will delete that component when it is deleted
itself. If you pass NULL then your component should delete it in the
destructor. If you pass 'this' then it will be deleted automatically
provided that OwnerMbx is a vcl object.

>     if (AsServer)
>     {
>         // create TCP Server Socket, with default parameters
>     }
>     else
>     {
>         // create TCP Client Socket, with default parameters
>     }

Seeing that you make one class that can behave both like server
and client I shiver. I have done such things too but now my opinion
is that live is much easier having two classes. Maintainability
of code only for a server and only for a client is much easier then.

Hans.