[Communicator-user] multiple connection help

[David Wade-S. <st...@cs...>]

Greetings.

I'm far from a Communicator expert, so I'm helping someone can point me 
in the right direction.

We've built an "Interactive Book" which is "architected" as follows: On 
the PC/Mac client, we use Java to display the layout of the book, and 
perform animation. This client connects to a Linux server which houses 
servers to perform text-to-speech synthesis, speech recognition,  speech 
alignment, and so on.

The server applications are running in Galaxy Communicator, as you might 
expect. In order to allow client connections, I wrote a Galaxy 
"bridging" server to accept connections from a client machine, and send 
data (text or audio) back and forth to the other servers in Galaxy. So 
the Java client connects to Galaxy via a socket-based connection to the 
"bridging" server.

The system works, but now it's time to consider multiple clients. I'm 
trying to understand the Galaxy documentation with respect to threads, 
but it seems a little sparse, at least for me, and in addition, I don't 
even know if what I want to do is possible.

The way I envision handling multiple clients is to have my bridging 
server act like a standard Unix daemon: It accepts a connection from a 
client, then forks a child who handles that client and goes back to 
listening for more connections. But that would mean I would have 
multiple bridging processes, all of whom are Galaxy Communicator 
servers. Possible?  If not, is there another way this can be accomplished.

Thanks in advance for any suggestions, pointers, help, etc.

Dave