If you are using server sockets (ie to receive requests from the Outside World), what kinds of things are you using them for? I'm mostly curious about the protocols you're using (http or ftp or whatever)
This doesn't cover using client sockets (for *making* requests to outside services).
Thanks,
-- peter
One use I have made in the past was with the primary server inside a firewall and a small box outside the firewall where the small box was used for communication to and from an [extremely stupid] warehouse system and the small box and the primary server exchanged message traffic.
One use I have made in the past was with the primary server inside a firewall and a small box outside the firewall where the small box was used for communication to and from an [extremely stupid] warehouse system and the small box and the primary server exchanged message traffic.
Flag this post as spam/abuse.
The customer in question was acquired by a much larger publisher, so the system is long since not in use. Yes, as I recall, the message was proprietary and structured for the purpose. Outbound we were sending picking slips and inbound they were shipping notices and inventory changes.
Peter, writing a http/ftp server in 4gl makes little sense imho albeit we can say we share the same single-threaded model as node.js :)
Did wrote Ganimede (http://sf.net/p/ganimede) when sockets were made available in V9, proprietary protocol though... basically I find it much easy to have the message length stated upfront (long) then once everything is read the message gets processed, still this doesn't work well with streaming but not looking into streaming video from 4gl either.
To be sure, the application I referred to worked as well as it did because there was only the one other end point and the message frequency was not very high. I'd hate to have to do anything very interesting without multi-threading.