[Autogenerated] As we've seen session zero name space,
is under base named objects here.
So, to be more precise the objects.
That we see here.
Are named objects created either by session zero processes
or perhaps created by other processes.
That are part of different sessions.
But they use the global back slash prefix in order for these objects,
to land in zero, in the zero, in the session zero,
namespace So what does global look like?
And Why does it actually work?
So let's look at an example for session, two let's say here.
Based named object.
If I use the global prefix in fact,
you can see the global does exist here as a symbol link CLI and You notice
it actually points two base named objects under the root.
And then If we add to that after the back,
slash the name of the object like shutdown,
event it will turn up in session zero, namespace So here's a quick example,
let's go ahead.
And go back, to our application here.
And just close that and change here.
The the code to create the object under session zero name
space by prefixing the name shutdown, event with global.
So if we do that let me run an instance here we should find shutdown,
event appearing in session zero, namespace So here shutdown,
event doesn't exist anymore.
We don't see shutdown, event under base named object in session,
two Let's try this again.
Just to Make sure and you can see that It doesn't exist here
but it should exist in base named objects.
So if we search here, we should find our shutdown,
event Here it, is There's a single handle,
that which we just created.
So using that global back, slash allows us to share objects between sessions.
By the way, UWP processes,
you might think they might use the same trick in order to
share objects with other processes, but they can't,
they can't in terms of security.
They are not allowed.
To create objects in session zero, namespace at all.