Closed Bug 1223722 Opened 10 years ago Closed 10 years ago

Transfer strongly typed values in |BluetoothValue|

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(firefox46 fixed)

RESOLVED FIXED
2.6 S5 - 1/15
Tracking Status
firefox46 --- fixed

People

(Reporter: tzimmermann, Assigned: tzimmermann)

References

Details

Attachments

(3 files, 3 obsolete files)

Many value are transfered as nsString in |BluetoothValue|. They should be stored in dedicated types instead.
Assignee: nobody → tzimmermann
Hi! This is the patch set for sending typed values from parent to content process. Currently these values are sent as |nsString|.
Comment on attachment 8699403 [details] [diff] [review] [01] Bug 1223722: Transfer Bluetooth addresses in |BluetoothValue| Sorry, I would like to forward the review request to Bruce since I'll be on PTO from 12/23 to 1/6. Thanks a lot for your help, Bruce.
Attachment #8699403 - Flags: review?(joliu) → review?(brsun)
Attachment #8699404 - Flags: review?(joliu) → review?(brsun)
Attachment #8699405 - Flags: review?(joliu) → review?(brsun)
Comment on attachment 8699403 [details] [diff] [review] [01] Bug 1223722: Transfer Bluetooth addresses in |BluetoothValue| Review of attachment 8699403 [details] [diff] [review]: ----------------------------------------------------------------- LGTM ::: dom/bluetooth/common/webapi/BluetoothPairingListener.cpp @@ +53,4 @@ > const nsAString& aPasskey, > const nsAString& aType) > { > + MOZ_ASSERT(!aName.IsEmpty() && !aType.IsEmpty()); nit: the assertion for |aAddress|
Attachment #8699403 - Flags: review?(brsun) → review+
Comment on attachment 8699404 [details] [diff] [review] [02] Bug 1223722: Transfer Bluetooth remote names in |BluetoothValue| Review of attachment 8699404 [details] [diff] [review]: ----------------------------------------------------------------- LGTM
Attachment #8699404 - Flags: review?(brsun) → review+
Comment on attachment 8699405 [details] [diff] [review] [03] Bug 1223722: Transfer arrays of Bluetooth UUIDs in |BluetoothValue| Review of attachment 8699405 [details] [diff] [review]: ----------------------------------------------------------------- Basically it looks good to me. It would be good to add comments in codes or in commit messages to describe more about the reason why sorting stuffs are moved from the parent process to the content process. The decision making would be interesting and worth being noted.
Attachment #8699405 - Flags: review?(brsun) → review+
(In reply to Bruce Sun [:brsun] from comment #8) > Comment on attachment 8699405 [details] [diff] [review] > [03] Bug 1223722: Transfer arrays of Bluetooth UUIDs in |BluetoothValue| > > Review of attachment 8699405 [details] [diff] [review]: > ----------------------------------------------------------------- > > Basically it looks good to me. > > It would be good to add comments in codes or in commit messages to describe > more about the reason why sorting stuffs are moved from the parent process > to the content process. The decision making would be interesting and worth > being noted. That's a good point. I will add a rational in the patch's next iteration.
Changes since v1: - added missing |MOZ_ASSERT| for address
Attachment #8699403 - Attachment is obsolete: true
Attachment #8704078 - Flags: review+
Changes since v1: - fixed incorrect type when setting device name (string->remote name)
Attachment #8699404 - Attachment is obsolete: true
Attachment #8704079 - Flags: review+
Changes since v1: - added rational to commit message
Attachment #8699405 - Attachment is obsolete: true
Attachment #8704080 - Flags: review+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: