Home Original page

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult by kannanjgithub · Pull Request #11666 · grpc/grpc-java

@kannanjgithub 

…ization context to call it from inside of the synchronization context.

Fixes grpc#11662.

ejona86

@kannanjgithub

@kannanjgithub kannanjgithub changed the title api: Listener2.onResult2 can only be called from within the synchronization context api: Use synchronization context when forwarding from Listener onAddresses to Listener2 onResult2

Nov 5, 2024

@kannanjgithub kannanjgithub changed the title api: Use synchronization context when forwarding from Listener onAddresses to Listener2 onResult2 api: When forwarding from Listener onAddresses to Listener2 continue to use onResult

Nov 5, 2024

kannanjgithub added a commit to kannanjgithub/grpc-java that referenced this pull request

Nov 14, 2024 
…to use onResult (grpc#11666)

When forwarding from Listener onAddresses to Listener2 continue to use onResult and not onResult2 because the latter requires to be called from within synchronization context and it breaks existing code that didn't need to do so when using the old Listener interface.

kannanjgithub added a commit that referenced this pull request

Nov 14, 2024 
…to use onResult (#11666) (#11688)

When forwarding from Listener onAddresses to Listener2 continue to use onResult and not onResult2 because the latter requires to be called from within synchronization context and it breaks existing code that didn't need to do so when using the old Listener interface.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators

Feb 26, 2025