×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Gqcy wrote:
as I understand it...
it is a term used in "asynchronous" languages (javascript) in which
a callback will be a method of the "base program" checking on the
"asynchronous" program to see if it is done, and to receive the results...
Sort-of.
It isn't limited to "asynchronous" languages, or to multi-threaded
languages. And indeed, the concept, if it's the one I think you're
talking about, is used fairly extensively in things like Scott Klement's
HTTPAPI.
This is just my understanding of the concept I *think* you're referring
to, but . . .
Imagine the following situation:
You're calling an API of some sort, that does some standardized process,
and produces results of some sort, and it defaults to, say, pouring
those results into a stream file in the IFS. But instead of that you
want to process those results directly in your own code, as they arrive.
So you pass, as one of the parameters to the API call, a procedure in
your own code, which the API then calls, whenever it has results for
your program to process.
--
JHHL
This mailing list archive is Copyright 1997-2024 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
