What I know about web programming would fit into a thimble. However, I
can't imagine all users would be scrolling through the same area, etc. But
a gut feeling is that it might be hard to do so. Imagine you have a keyed
data queue. Your ODBC programs call a stored procedure. The stored
procedure dings fills a data queue with a request for data. Then it waits
on a keyed data queue for the results. Then your NEP reads from the first
data queue. Sees the request. And fills the keyed data queue with the

What would be in the first data queue? Well, how's about:
- A unique request id
- A key position
- How many rows to return.
- Forward, or backward, from the key.
Then the keyed data queue would have, as it's key, the unique request id,
and the number of rows requested. And maybe one of the fields in the row
could have a default value to indicate end of file.

Rob Berendt

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].