Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dbus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 247
    • Issues 247
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dbus
  • dbus
  • Issues
  • #364

Closed
Open
Created Dec 11, 2021 by diwic1@diwic1

Large messages need many calls to dbus_connection_read_write

Hi,

A user of the Rust libdbus bindings have reported that large messages may take several rounds of calls to dbus_connection_read_write to receive a large message. We speculate that every call to dbus_connection_read_write can only receive 2048 bytes from the socket, regardless of the value of timeout_milliseconds.

This seems like a bug to me, but if it is intended behavior then it should be clearly documented, and also there needs to be an API call to figure out whether or not one should call dbus_connection_read_write again.

Issue reference: https://github.com/diwic/dbus-rs/issues/364

Edited Dec 11, 2021 by diwic1
Assignee
Assign to
Time tracking