For searching in real time fashion from browser side , i was wondering
which is better -
For each keypress , a request is sent.
If the request have not retured by next key press , either i can
Wait till the current request is done and run the new request only
when this is done.
Or i can abort the current request and move to the new one.
On the second approach i was wondering what will happen at elasticSearch
side , will the request would be still processed if the request is aborted
by the client ?
For searching in real time fashion from browser side , i was wondering
which is better -
For each keypress , a request is sent.
If the request have not retured by next key press , either i can
Wait till the current request is done and run the new request only
when this is done.
Or i can abort the current request and move to the new one.
On the second approach i was wondering what will happen at elasticSearch
side , will the request would be still processed if the request is aborted
by the client ?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.