-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move autocomplete to server #226
Comments
My concern is latency. It takes around 1s from my location for server to respond. |
We can prime and cache - or open up the connection early. Good/useful result trumps latency here, and it's something we should deal with. |
On my latency argument: Maybe we can write the autocomplete logic in such a way that we can use it a ServiceWorker to imitate the service locally (or maybe even a Cloudflare worker). |
Yes, either of those (or together) could work. We’d have to check how much it would cost to use the cdn tho. Our goal should be 100ms query response time. |
A few issues with auto-complete on the client...
CodeByDefault
wit the type and what spec a term declared in, etc. directly in the autocomplete).We should allow the server to stream autocomplete results.
The text was updated successfully, but these errors were encountered: