Suggestion about connection migration which makes it more generic

[Tinker Tan]

Hi,

As far as I know,  the connection migration in cronet relys on NetworkChangeNotifier which implemented in diffrent ways on each platform(Android or iOS).

It makes connection migration difficult to be widely used.Following reasons:

1. iOS hasn't implement NetworkChangeNotifier.

2. Android  OS >= Lollipop(5.0) implement NetworkChangeNotifier but still some phones under Lollopop.

3. For native usage, for example: quic_transport_client, quic_toy_client or app only use native cronet interface, they can't do connection migration.

And I have made some repairs which not rely on NetworkChangeNotifier or specific OS interface. It works well on iOS/Android. Connection migration has maintained a high success rate even on windows PC while switching network-interface.

So, would you consider to accept this generic solution for connection migration?

[David Schinazi]

Hi,

We'd love to find out more about how your proposal works.

Could you show us the code?

Thanks,

David

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/bc0fc71f-8568-479f-9c50-b7d29561bbeen%40chromium.org.

[Tinker Tan]

I'm glad to do it.

By the way,  Is my analysis about cronet correct? Does chromium have a plan to solve the problem before?

[David Schinazi]

Yes, your analysis is correct: connection migration currently relies on the NetworkChangeNotifier.

David