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.

Sign up for GitHub

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

Jump to bottom

[Flight Reply] Encode Objects Returned to the Client by Reference #29010

Merged
merged 3 commits into from
May 10, 2024
Merged

[Flight Reply] Encode Objects Returned to the Client by Reference #29010

merged 3 commits into from
May 10, 2024

Commits on May 9, 2024

  1. Store temporary references by object

    @sebmarkbage
    sebmarkbage committed May 9, 2024
    Configuration menu
    Copy the full SHA
    a5bd018 View commit details
    Browse the repository at this point in the history

  2. Encode temporary by the path it's stored 

    This lets us also register objects that are not opaque by reference.
    @sebmarkbage
    sebmarkbage committed May 9, 2024
    Configuration menu
    Copy the full SHA
    73098e2 View commit details
    Browse the repository at this point in the history

  3. Use an explicit temporary reference set on the server 

    This ensures that objects can only be passed by reference if they're
part of the same pair of renders.

This also ensures that you can avoid this short cut when it's not possible
such as in SSR passes.
    @sebmarkbage
    sebmarkbage committed May 9, 2024
    Configuration menu
    Copy the full SHA
    7c69449 View commit details
    Browse the repository at this point in the history