🚀 go-pugleaf

Thanks for all your input.

All of you have mentioned adding a message Q to the thread, where can I get 
info on this?

Thanks

Paul

PS. I will look at the indy project site also.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4341ae16$3@newsgroups.borland.com...
>
> "Paul" <plmacca@clara.co.uk> wrote in message
> news:433e524d$1@newsgroups.borland.com...
>
>> I've written some classes to wrap the server and client components
>> (and serial) to create some connectivity classes.
>
> You might consider using a pre-written library that already does all of 
> that
> for you.  Indy (http://www.indyproject.org), for instance.  In particular,
> due to Indy's plugin architecture, adding serial port support would take
> minimal effort.
>
>
>> But if I try to instantiate the class(es) in a thread, then only the
> serial
>> connectivity works.  The server and client socket fail (such as it never
>> gets the events to show client connecting or connected).
>
> Non-blocking notifications are message-based.  Thus your thread would need
> its own message queue to dispatch the notifications properly.  If that 
> does
> not suit your needs, then you will have to use blocking sockets instead,
> which means that you will not need a message queue at all, but you will
> likely have to re-think your read/writing strategy a bit.
>
>
> Gambit
>
>