Skip to content

ios: use internal engine thread#530

Merged
rebello95 merged 1 commit intomasterfrom
thread-ios
Oct 21, 2019
Merged

ios: use internal engine thread#530
rebello95 merged 1 commit intomasterfrom
thread-ios

Conversation

@rebello95
Copy link
Contributor

@rebello95 rebello95 commented Oct 21, 2019

Recent changes (namely #498) made it unnecessary for the platform-level clients to start Envoy on newly spawned threads. In fact, these changes actually introduced potential races where consumers of the platform clients could end up calling send on engines that hadn't finished starting on these threads.

This PR removes the custom threading logic in Swift in favor of simply using the new threading being done within the core. Another PR will make the same change on Android: #531.

Signed-off-by: Michael Rebello me@michaelrebello.com

Recent changes (namely #498) made it unnecessary for the platform-level clients to start Envoy on newly spawned threads. In fact, these changes actually introduced potential races where consumers of the platform clients could end up calling `send` on engines that hadn't finished starting on these threads.

This PR removes the custom threading logic in Swift in favor of simply using the new threading being done within the core. Another PR will make the same change on Android.

Signed-off-by: Michael Rebello <me@michaelrebello.com>
@rebello95 rebello95 requested a review from junr03 October 21, 2019 23:06
Copy link
Member

@junr03 junr03 left a comment

Choose a reason for hiding this comment

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

Yep, this is what I had in mind based on our discussion

@rebello95 rebello95 merged commit ce087f7 into master Oct 21, 2019
@rebello95 rebello95 deleted the thread-ios branch October 21, 2019 23:13
junr03 added a commit that referenced this pull request Oct 22, 2019
Description: "Recent changes (namely #498) made it unnecessary for the platform-level clients to start Envoy on newly spawned threads. In fact, these changes actually introduced potential races where consumers of the platform clients could end up calling send on engines that hadn't finished starting on these threads."

This PR removes the custom threading logic in Kotlin in favor of simply using the new threading being done within the core. Parallel to #530.
Risk Level: med - reduce threading complexity
Testing: local app.

Signed-off-by: Jose Nino <jnino@lyft.com>
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

Successfully merging this pull request may close these issues.

2 participants