Skip to content

Stop sending requests in call init #848

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

Merged
merged 2 commits into from
Jun 24, 2020
Merged

Conversation

glbrntt
Copy link
Collaborator

@glbrntt glbrntt commented Jun 18, 2020

Motivation:

Previously @Lukasa noted that we did some networking in the call init's
which isn't ideal. I forgot that calls are made though an internal
class, so it is indeed possible to move the networking calls.

Modifications:

  • Move networking calls to just after the call object is created
  • Shuffling code about, no real functional changes

Result:

  • No networking in the *Call inits
  • Cleaner inits
  • Nothing functional

Motivation:

Previously @Lukasa noted that we did some networking in the call init's
which isn't ideal. I forgot that calls are made though an internal
class, so it is indeed possible to move the networking calls.

Modifications:

- Move networking calls to just after the call object is created
- Shuffling code about, no real functional changes

Result:

- No networking in the *Call inits
- Cleaner inits
- Nothing functional
@glbrntt glbrntt added nio 🔨 semver/patch No public API change. labels Jun 18, 2020
@glbrntt glbrntt requested a review from Lukasa June 18, 2020 13:59
Copy link
Collaborator

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You made transport public on your 4 call objects so that the connection objects can invoke it. Would it be better to keep it private and instead have the call objects implement that method, and then just call it on their private object?

@glbrntt
Copy link
Collaborator Author

glbrntt commented Jun 18, 2020

You made transport public on your 4 call objects so that the connection objects can invoke it. Would it be better to keep it private and instead have the call objects implement that method, and then just call it on their private object?

100%. Will update, thanks.

@glbrntt glbrntt requested a review from Lukasa June 24, 2020 08:27
Copy link
Collaborator

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic, I like this patch a lot.

@glbrntt glbrntt merged commit 1f272f8 into grpc:master Jun 24, 2020
@glbrntt glbrntt deleted the gb-simpify-init branch June 24, 2020 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants