Skip to content
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

Open
marcoscaceres opened this issue Jul 27, 2021 · 4 comments
Open

Move autocomplete to server #226

marcoscaceres opened this issue Jul 27, 2021 · 4 comments

Comments

@marcoscaceres
Copy link
Collaborator

A few issues with auto-complete on the client...

  1. it downloads 500kb in terms
  2. it do doesn't include the type information + other potentially useful things - so we can't style the autocomplete in useful ways (e.g., IDL things should be shown 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.

@sidvishnoi
Copy link
Member

My concern is latency. It takes around 1s from my location for server to respond.

@marcoscaceres
Copy link
Collaborator Author

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.

@sidvishnoi
Copy link
Member

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).

@marcoscaceres
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants