Subject | RFC: Reverse Query |
---|---|
Author | Gerhardus Geldenhuis |
Post date | 2002-03-04T08:12:19Z |
Hi
I had an idea to do a kind of reverse query what I meant is that the user
would submit a query "select * from sales where date=today" which would be
submitted to the db and the data send to the user. The reverse part comes in
that the user says he always want the newest and up to date version of the
query. That would mean when requesting the server would register that the
user wants this and send him the data as the query changes. The idea is to
evaluate transactions submitted and see if they would have an effect on the
reverse query and if so send the user the data.
Typical application would be were you would want to see to the minute values
without resubmitting(refreshing) every 30 seconds. The tradeoff would
posibly be a slower server but far less network traffic.
Groete
Gerhardus
I had an idea to do a kind of reverse query what I meant is that the user
would submit a query "select * from sales where date=today" which would be
submitted to the db and the data send to the user. The reverse part comes in
that the user says he always want the newest and up to date version of the
query. That would mean when requesting the server would register that the
user wants this and send him the data as the query changes. The idea is to
evaluate transactions submitted and see if they would have an effect on the
reverse query and if so send the user the data.
Typical application would be were you would want to see to the minute values
without resubmitting(refreshing) every 30 seconds. The tradeoff would
posibly be a slower server but far less network traffic.
Groete
Gerhardus