|
Hi, > > Why do you prefer using sockets or pipes? Just curious. > I don't like the fact that data queues won't produce an error if there's no program listening for data on them. I want to know that the program on the other end is listening and responding in real-time. I'm not usually interested in storing data or queueing it up to be processed later. I'm interested in real-time program to program communications. I also prefer sockets for portability. Sure, IBM has APIs for sending data queues on Windows, but you have to install their software and pay them for it's use. When I want to go to another platform such as Unix, data queues aren't available at all. They're not an industry standard, they're an IBM proprietary thing. Sockets, however, are available everywhere and are integrated into every operating system. I have scales (for weighing products) that I can write programs on and that have a sockets interface. They certainly don't have a data queue! This is not an absolute thing, however. I do use data queues, and there are places where they're more appropriate. However, for me it's been rare that I use them.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.