Ideas on XNamespace.

[b-aaz]

Describe the idea

The TL;DR:

I think the XNamespaces should be handled at runtime by an entity similar to the Window Manager, (it could be the WM itself).

---

XNamespaces are currently handled by setting a list of process names and their "namespace" in a config file before the server is initiated, this is understandable for a POC, but if we aim to turn this extension to a widely used technology, we should create a more accessible means of managing these namespaces.

I believe we should walk in the spirit of X11 and provide "unopinionated" APIs that can be used in various scenarios and use cases. An example of these APIs is the simple XWindowMap and XWindowUnmap which are used for minimizing windows, but can also be used to create virtual desktops.

My current idea of how these APIs would look like is the following:

1. There should be a function (or a similar means for) returning the current list of namespaces.
2. There should be a set of functions that create and destroy namespaces.
3. A method should be available for configuring a namespace and the resources it has access to.
4. Some method should exist for ensuring a new window is created in a given namespace. This is to enable the WM's program launchers to have a "right click menu" that can ensure a new program is lunched in a given namespace.
5. A set of functions should be available for adding and removing a window from a namespace.
6. It should be possible to get the namespace a given window belongs to. This can be used by the WMs to decorate windows in different colors based on their namespace.
7. A possible event can be sent to a window if its namespace changes.

Like the Window Manages role, only a single process should be able to claim this role and have access to these methods. Other processes can only get this role after the previous Namespaces Manager releases its position.

The role of Namespace Manager in most cases would be claimed and used by the Window Manager.

This is currently just a mental map of things, not a reference. We should discuss this further and create an actual spec in the future,

Extra fields

• I have checked the existing New Ideas, RFCs Of The Core Team, Ideas Soon To Be Addressed and Someday Ideas
• I have read the Contributing Guidelines
• I'd like to work on this idea

[probonopd]

Not sure I understand the whole concept well enough yet, but I imagine...

• By default, start each X11 application in its own namespace
• By right-clicking on the window decorations, the window manager could bring up a menu for the user to "join namespace"
• This application would then be part of the chosen namespace instead of having its own
• This would need to be persisted
• Similarly, there should be a GUI to remove applications from existing namespaces
• Depending on the namespace, the window manager could render the window decorations differently (different colors, namespace in the title bar, things like that)
• Reading and changing namespaces could be done by using X11 Atoms

Something like that?

[callmetango]

Thank you for adding your idea! At the moment, I'd just like to add some…

Additional information

Only FYI: There some other discussions or pull requests about improving Xnamespace or the associated security context in XLibre:

• Improve X11 security · X11Libre · Discussion #63
• Improving Clipboard security · X11Libre · Discussion #84
• security-feature: Integration permission management system by GermanAizek · Pull Request #1627 · X11Libre/xserver
• expand namespace by squishypinkelephant · Pull Request #1628 · X11Libre/xserver