After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698125 - gupnp: Notification sequence numbers are int, should be uint32
gupnp: Notification sequence numbers are int, should be uint32
Status: RESOLVED FIXED
Product: GUPnP
Classification: Other
Component: gupnp
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GUPnP Maintainers
GUPnP Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-16 12:25 UTC by Jens Georg
Modified: 2013-05-29 13:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
SEQ is supposed to be an uint32 (2.96 KB, patch)
2013-05-29 10:32 UTC, Jens Georg
committed Details | Review

Description Jens Georg 2013-04-16 12:25:56 UTC
UDA says sequence numbers can be implemented as an unsigned 32 bit integer:

"Event messages are tagged with an event key. A separate event key must be maintained by the publisher for each subscription to facilitate error detection (as explained below). The event key for a subscription is initialized to 0 when the publisher sends the initial event message. For each subsequent event message, the publisher increments the event key for a subscription, and includes that updated key in the event message. Any implementation of event keys should handle overflow and wrap the event key from 4294967295 back to 1 (not 0). Subscribers must also handle this special case when the next event key is not an increment of the previous key. Should be implemented as a 4 Byte (32 bit) unsigned integer."
Comment 1 Jens Georg 2013-05-29 10:32:46 UTC
Created attachment 245540 [details] [review]
SEQ is supposed to be an uint32
Comment 2 Jens Georg 2013-05-29 13:40:08 UTC
Attachment 245540 [details] pushed as 1c515b9 - SEQ is supposed to be an uint32