Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • xserver xserver
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 944
    • Issues 944
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 130
    • Merge requests 130
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • xorgxorg
  • xserverxserver
  • Issues
  • #1428

RFE: XGE generic event channels

The Present extension makes the notable improvement that events are selected and delivered relative to an EVENTID type - "event channel" might be a better name. This allows for multiple subsystems within a process to receive a copy of any given event, without affecting other subsystems or needing to rely on a client-side convention for event queue interest. (Well. Kinda. It bakes that convention into libxcb as "special events". Whatever.)

Unfortunately it stops there, and it doesn't really belong there. Event channels ought to be an XGE extension concept, and they should be able to encapsulate arbitrary core or extension events. This could massively improve life on the client side. A few examples off the top of my head:

  • Multiple readers could listen for ConfigureNotify on the root window, or corresponding RANDR events, and all would get notified
  • llvmpipe would be able to use the send_event=True version of ShmPutImage to increase parallelism
  • libX11 could potentially internally redirect event selection to its own private channel, which might finally solve the "who owns the event queue" problem when mixing xcb and xlib in one process
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking