|
Quote: The fundamental problem with data queues is your client code does not get a definitive return code from the server. ...I handled that with a 2-way data queue process like described before.
With a program call none of these issues have to be addressed. -Steve ==>> You can resolve those issues easily in a one time deal --once--, do up two program calls if you want (or service program subproc), and after that you don't have to think about it. Using subprocs especially, with const and all, you don't even have to think about data lengths, or key lengths, or user-id, except the once. --Alan
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.
midrange.com
