RE: Local Sockets vs. Data Queues

Hi Tom and Scott

I'm really having trouble trying to picture how this could be easier if the
server process is on the same machine as the proposed socket. Can someone
enlighten me how this would be less work ?

I've used data queues many times to control server processes but if there's
a better way I'm all ears.

BTW Scott, the two way communication - I find it easier to just have a
queue for each process. Part of the information a job sends to the server
on it's queue is the name of the queue to respond on. Obviously this takes
some planning up front but works pretty well. Apologies if you already had
this figured; I'll be surprised if you hadn't ! :)

Regards
Evan Harris

>Thanks Scott.  I was thinking about AF_UNIX in particular.  Mulling over
>ways to control a server process....  Dtaq is easier but as you say,
>requests queue up.  Which in this case wouldn't be good.  I also thought
>about using the signal APIs but why give myself a headache?  Looks like
>socket might be the way to go.