> -----Original Message-----
> From: Jack Nickels [mailto:[log in to unmask]]
> 
> We have a requirement for ... data synchronization ...
> use[ing] Sockets ...
> 
> the HP3000 ... listener program ... spawns another program 
[on each connection]

this is fairly typical of socket-oriented programming
 
[...]
> We are looking at huge volume of requests ... will the HP3000 ...
> support ... 1000 transactions per minute?

1000 trx/minute = 16.66 trx/second, which gives you about .06 seconds to do whatever you need before things start to back up.

> Please note that the HP3000 side processing is very fast and 
> happens in milliseconds if the transactions are send independantly.

Well, as I said, you've got about 60 milliseconds to do what you need to do -- only you will know if this is enough or not.

> Welcome to any alternate suggestions as well apart from sockets

If process spawning overhead becomes too much, you might consider placing the bulk of the process into a daemon-like program that communicates via pairs of message files, then your "socket" program can be made a bit more "lightweight" in that it only translates socket calls to message file reads/writes [hint: you can use interrupts instead of polling...]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *