Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
wayland
wayland
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 25
    • Merge Requests 25
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • waylandwayland
  • Issues
  • #106

Closed
Open
Opened Jul 22, 2019 by Simon Ser@emersionOwner

Versioned wl_registry

Disclaimer: this is just a wild idea, don't take it too seriously. I have no idea what the implications of this would be. Also, some might call it a hack (it is).

While talking about #10 (closed), kennylevinsen has suggested a way to make wl_registry versioned. We could keep object ID 1 as wl_display v1 (which creates a wl_registry v1), but also advertise the wl_registry as a regular global, possibly with a higher version. This way, clients can bind to it and get extra functionality.

The annoying thing is that clients that are willing to use a higher wl_registry version will need to bind twice (and will receive twice the list of globals).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/wayland#106