Hi Luiz, >> And the info command only prints out the Session/Status/Size/Transferred >> properties and does not print out the others as below: >> >> # info /org/bluez/obex/server/session1/transfer0 >> Transfer /org/bluez/obex/server/session1/transfer0 >> Session: /org/bluez/obex/server/session1 >> Status: active >> Size: 18446744073709551614 >> Transferred: 262010 >> [CHG] Transfer /org/bluez/obex/server/session1/transfer0 Transferred: 294771 (@32KB/s 428259:52) > > I think the idea was to omit the Size in case the header has not been > read, or is not available, though perhaps that needs fixing in both > obexd really omit if the size is 0 and perhaps disable progress if the > size is unknown. The documentation already indicates Size is optional > but the implementation does not add a exists callback, but Im not sure > why that would appear as the value above instead of 0. It seems that the value is OBJECT_SIZE_DELETE (-2). When I tentatively removed OBJECT_SIZE_DELETE at obex_session_start(), the info command printed out 0 as the Size property. So I think that obexd may emit the Size property after starting a session and before getting a file size. I will try to dig this behavior. Regards, Eramoto -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
