🚀 go-pugleaf

> I might be missing something here, or misunderstanding your design or 
> problem.  But it seems you want to pass a string and assoc ID to the 
> thread, to then call sctp_send to send this information?

Yes.


> Why don't you just call the send method in the thread with (stack based) 
> parameters rather than globals:
>
>    if (sctpThread)
>        sctpThread->Send( String(buffer),  associationID[Site] )

That's the effect I'm trying to achieve, but I'm having trouble figuring out 
a thread-safe method of doing that.


> Then make the Send method thread safe with a critical section to do any 
> actions that need it (around adding or removing items from lists / 
> queues).

If the parameters are passed in, how/where do I put in a critical section 
lock?  And does that do anything to help the scope problem if the VCL thread 
has gone on to something else by the time the SCTP thread picks this up?


> eg. put the parameters passed in on to a queue, and signal the thread 
> there is a job to do.  The thread then wakes up, and removes the oldest 
> job from the queue thread safely, until the queue is empty.

How do I do that?