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

[VK Company Feedback] FPS domains limit #71

Closed
NekR opened this issue Nov 2, 2021 · 1 comment
Closed

[VK Company Feedback] FPS domains limit #71

NekR opened this issue Nov 2, 2021 · 1 comment

Comments

@NekR
Copy link

NekR commented Nov 2, 2021

Hi! What is planned limit on domains in single FPS and what would be "too big" for browsers to handle effectively?

For example, we probably have thousands of domains. They all aren't probably needed in FPS, but it certainly might be needed to include all of them in there at some point.

@krgovind
Copy link
Collaborator

@NekR - The question of limiting the size of a set is being discussed on #29, could you please comment on that issue instead? It would be useful if you can think about how many of these domains need to be in the same set. Do all of these thousands of domains interact with each other, or have a user flow that encompasses all the domains?

The question of appropriate limits is still an open question, but we're looking for feedback to help inform that decision.

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