QuickGrid virtualization sample should not hit FDA server

[kg]

When scrolling around in the QuickGrid virtualization sample it makes a lot of small requests to the FDA.gov API server. I really don't think it's a good idea to use this server for a production demo if hitting the down arrow 1-4 times or clicking the scrollbar once is enough to kick off a network request. The response times are already upwards of 100ms for me and I feel like if we generate load on it from our documentation they're going to block us outright, it would be better to leave this API to be used by people who need it. The sample should probably hit a synthetic API endpoint that just does a sleep() of sufficient length to let the user see the virtualization.

The tuning values for the sample would also need to be adjusted if using a third party's server, I think, so that it generates fewer, larger requests. But it's better to not need to worry about it.

[SteveSandersonMS]

The sample should probably hit a synthetic API endpoint that just does a sleep() of sufficient length to let the user see the virtualization

It's difficult to illustrate the functionality properly without a real HTTP endpoint that you can see being hit in the browser network tab. And we can't provide a real HTTP endpoint ourselves (one that produces different results based on arbitrary parameters) because this has to be hosted on a static-only host.

The most realistic alternative I can imagine would be using a service worker to simulate the existence of an HTTP endpoint, but it would still be difficult to provide large amounts of realistic-looking data without actually downloading a lot of data to the client for the service worker to use.

[kg]

The sample should probably hit a synthetic API endpoint that just does a sleep() of sufficient length to let the user see the virtualization

It's difficult to illustrate the functionality properly without a real HTTP endpoint that you can see being hit in the browser network tab. And we can't provide a real HTTP endpoint ourselves (one that produces different results based on arbitrary parameters) because this has to be hosted on a static-only host.

A $5/mo VPS could probably host this service, though I understand that it's not a single click of a button to set one up. I would offer to host it myself, but having .NET docs point to someone's personal server is probably undesirable.

The most realistic alternative I can imagine would be using a service worker to simulate the existence of an HTTP endpoint, but it would still be difficult to provide large amounts of realistic-looking data without actually downloading a lot of data to the client for the service worker to use.

Wouldn't it be an option to download a snapshot of these government datasets once at startup (we could serve this from the static-only host), then serve slices of it from a service worker?

[SteveSandersonMS]

serve slices of it from a service worker?

Service workers run inside the browser, so it would only be able to serve slices of a dataset that have been downloaded by that browser. That's what I meant by "without actually downloading a lot of data to the client". TBH if it was < 200KB compressed, say, it would probably be OK if someone wrote a PR (but I wouldn't expect the ASP.NET Core team to get it to the top of their priority list soon)!

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.