939026 - B2G NetworkManager: resolveHostname() should use async dns service

Status: RESOLVED DUPLICATE of bug 1032097

(Firefox OS Graveyard :: RIL, defect)

Description

[Vincent Chang[:vchang][changyihsin]]

We should prevent any blocking call being used in main thread. 

Reference: https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIDNSService

Comment 1

[Ken Chang[:kenkai]]

Block a 1.3+ issue.

Comment 2

[Ken Chang[:kenkai]]

Chuck, please take this bug. It is a 1.3+ bug. Thanks.

Comment 3

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

This is the root cause of bug 991988

Comment 4

[chencong]

Would you  please give one patch on 1.3 ?
Thanks

Comment 5

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Hi Chencong,
Chuck is handling this issue. 
Let's move the discussion to bug 991988, as this one is duplicate.

Comment 6

[Bevis Tseng[:bevis][:btseng](Exited)]

We will provide another quick solution in 991988.
However, the solution here is still needed in the case that
either mms proxy or mmsc is not an ip-address.

Comment 7

[Bevis Tseng[:bevis][:btseng](Exited)]

Set to 1.3? to triage again.
This solution is only needed in the following condition of mms configuration in the target network:
1. mms proxy is available and is not an ip-address.
2. Or, mms proxy is not set and mmsc is not an ip-address.

In most of case, mms proxy is available and is an ip-address which is no need to be resolved.

Comment 8

[Bevis Tseng[:bevis][:btseng](Exited)]

This now depends on how we support bug 992772 in NetworkManager.

Comment 9

[Bevis Tseng[:bevis][:btseng](Exited)]

Bug 1032097 includes the solution of async-access to the DNSService.