Okay here's the situation. What I'm looking for, is a sort of generic
wrapper or API that will allow me to build threads with some kind of
messaging system attached with it. The idea is that these individual
threads will each handle small messages to each other, where each
thread managed to perform a seperate operation, yet their may be some
inter-dependance.

This is a Network based application, it recieves messages from client
machines, and then each message must be transmitted to a specific
thread. Don't worry about the incomeing networking message and how it
gets processed to the appropreate thread since that's pretty much
handled. So lets say I have Thread A and B. Sometimes, their will be
situations where A will want to send Data to B, then recieve a reply
from B, before continuing with it's job. What's the best way to do
that?

As for details, I'm looking for basic C code (obviously) that'll run
on a Sparc/Solaris 8+ machine. Sun Forte C 5.0 and GCC 2.95.3 are my
compilers of choice. Any thoughts? Anyone can point out any good code
examples for what I want?

Tony

In article <1121780380.703640.107030@o13g2000cwo.googlegroups .com>,
<gmtonyhoyt@yahoo.com> wrote:[color=blue]
>Okay here's the situation. What I'm looking for, is a sort of generic
>wrapper or API that will allow me to build threads with some kind of
>messaging system attached with it. The idea is that these individual
>threads will each handle small messages to each other, where each
>thread managed to perform a seperate operation, yet their may be some
>inter-dependance.[/color]

Troll.

gmtonyhoyt@yahoo.com writes:[color=blue]
> Okay here's the situation. What I'm looking for, is a sort of generic
> wrapper or API that will allow me to build threads with some kind of
> messaging system attached with it.[/color]
[...]

Standard C has no support for threads, so this is off-topic here.
You might try comp.programming.threads.

--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

On Tue, 19 Jul 2005 13:41:39 GMT, gazelle@yin.interaccess.com (Kenny
McCormack) wrote in comp.lang.c:
[color=blue]
> In article <1121780380.703640.107030@o13g2000cwo.googlegroups .com>,
> <gmtonyhoyt@yahoo.com> wrote:[color=green]
> >Okay here's the situation. What I'm looking for, is a sort of generic
> >wrapper or API that will allow me to build threads with some kind of
> >messaging system attached with it. The idea is that these individual
> >threads will each handle small messages to each other, where each
> >thread managed to perform a seperate operation, yet their may be some
> >inter-dependance.[/color]
>
> Troll.[/color]

Takes one to know one.

*plonk*

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

In article <8serd19n24275jse0ro27dn9a9d9qhjjc0@4ax.com>,
Jack Klein <jackklein@spamcop.net> wrote:[color=blue]
>On Tue, 19 Jul 2005 13:41:39 GMT, gazelle@yin.interaccess.com (Kenny
>McCormack) wrote in comp.lang.c:
>[color=green]
>> In article <1121780380.703640.107030@o13g2000cwo.googlegroups .com>,
>> <gmtonyhoyt@yahoo.com> wrote:[color=darkred]
>> >Okay here's the situation. What I'm looking for, is a sort of generic
>> >wrapper or API that will allow me to build threads with some kind of
>> >messaging system attached with it. The idea is that these individual
>> >threads will each handle small messages to each other, where each
>> >thread managed to perform a seperate operation, yet their may be some
>> >inter-dependance.[/color]
>>
>> Troll.[/color]
>
>Takes one to know one.[/color]

You would know.

(Rubber and glue...)