uWeave Receiver doesn't distinguish between connecting + receive data vs connected + receive data |
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Steps to reproduce the problem: N/a What is the expected behavior? uWeave Packet Receiver should have indication whether some data is received as a result of connection request/response versus data packets. This is because the packet receiver user might want to do something special when an connection is just established with some data appended in connection request/response versus just receiving regular data in data packets. What went wrong? Whether the data comes from connection request/response, the state will jump into DATA_READY and the code client has no way of determining whether DATA_READY is reached as the result of data appended on connection request/response versus regular data packets. Did this work before? No Chrome version: 52.0.2743.82 Channel: stable OS Version: Flash Version: Shockwave Flash 22.0 r0
,
Jul 29 2016
,
Jul 29 2016
,
Aug 5 2016
,
Aug 8 2016
,
Oct 28 2016
Can you say a little more about how this might be related to Chromium?
,
Nov 1 2016
bengr@: This bug refers specifically to this file: https://cs.chromium.org/chromium/src/components/proximity_auth/ble/bluetooth_low_energy_weave_packet_receiver.cc The original work was completed by an intern who has left Google. We will be continuing work on this shortly. Thanks!
,
Dec 12 2016
,
Dec 12 2016
,
Dec 12 2016
Looking into this, it seems there isn't much of a need for this behavior. It is easy to distinguish between connected ==> data ready and connecting ==> data ready by just observing the state before the packet is received. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by khorimoto@chromium.org
, Jul 28 2016