Re: Socket Question

Scott,

I would like eliminate the dtaq's.  This application is a two step 
process.  A store system connects via sockets to our corporate server, 
which spawns a server job, JobA.  JobA drops the data in the dataq waits 
for a response message on a separate dtaq.  JobB (t,he job discussed in my 
previous email) then receives the data from the dtaq, send it to the out 
for an approval, the puts the message on the second dtaq for JobA.  So the 
best solution would be to combine these two jobs so that the same job 
receives connections from our stores and sends the message to the outside 
vendor.  This would eliminate some other timing issues that occasionally 
cause problems.   However, I am not sure how to do this. I haven't really 
use the select( ) statement much.  Is this similar to your multiple client 
example in your tutorial?   How would this scale? As you correctly 
surmised, this is application handles a high volume of transactions. Would 
I just create multiple jobs, each listening on a different port? 

Thanks for all your help.  I am very appreciative of the list and the 
folks that are willing to help.

Mark Garton



If you could eliminate the data queues and do it all with sockets, then 
select() could be used to handle it all in one program.  I suppose you 
could have the data queues be read in a separate program in a separate 
job, and have it take the data queue data and send it via socket to the 
program that communicates with the vendor.  Then that vendor communication 

program could sit in select() loop and handle both sockets without delays.



------------------------------