Re: What's the connection between objects and threads?
On May 19, 7:08 pm, Szabolcs Ferenczi <szabolcs.feren...@gmail.com>
wrote:
On May 19, 11:22 am, James Kanze <james.ka...@gmail.com> wrote:
On May 19, 9:13 am, "Chris Thomasson" <cris...@comcast.net> wrote:
"Szabolcs Ferenczi" <szabolcs.feren...@gmail.com> wrote in message
news:53d7b28a-337b-4b8c-ae57-f88bf5b047cd@a1g2000hsb.googlegroups.com..=
..
On May 18, 11:43 am, darren <minof...@gmail.com> wrote:
3. A successful accepted connection is put into a queue (from the =
STL
library).
4. Meanwhile, back at the ranch, another thread is created and run=
ning
that continuously checks for entries into the queue.
Be aware that although STL is thread-safe to a certain extent,
:^/
Where does the current C++ standard say that the STL is
"thread-safe to a certain extent"???
And the implementations I use are completely thread safe, not
just to a certain extent.
After all your talking big, I doubt it, but if you wrapped the STL up,
maybe. But I am not sure about you.
I haven't wrapped anything. And judging from your previous
postings, I doubt you know what thread safety means, so I'm not
sure what your doubting means.
Can you show me how do you solve with plain STL container that
two consumer process are awaiting elements?
Can you ask a question that makes sense. STL containers are
data containers, they aren't thread synchronization elements.
No, you can't, until you wrap the STL and make the wrapped
container thread safe.
As I said, it's obvious that you don't know what "thread safe"
means.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34