[Autogenerated] As we've seen when you create objects with names from normal
user mode processes using the normal Windows API we get a name,
which is In fact, private, to a session.
We've seen that The names start with session, the number of the session.
Based named object, and then the actual name we provide.
So this is done intentionally.
So there's no mix up between different sessions creating objects.
That might have the same name if you do want to create names in
other directories or try to create names,
object names in different sessions.
Perhaps you might want to Try the native API the native
APIs such as anti creative event and similar APIs can work
with the full project manager, namespace Of course,
you might need certain permissions.
To be able to do that and So the redirection from the name that you
provide to the actual name created is automatic.
However, session zero as we've seen has a different layout in,
in, in where its directory actually resides under the root in win be J.
But in fact, one of the reasons that it's there, is that it's possible.
To share objects between sessions by using the name global back,
slash and then prefixing, that with the actual name.
So if I provide the name global back slash,
a BC, the a BC object will be created.
In the session zero, namespace That's kind of a way,
to share objects between multiple sessions.
A classic example,
is the case where you have a service running at session zero like
more services do and then You have a client application running in
section one or whatever the session number.
Is for the logged on user and they need to communicate by sharing
certain objects such as SSH shared memory object known as a file
mapping object or maybe be sharing,
a Mutt text or an event or whatever kind of an object you would like to share.
So in order to make that sharing work.
We have to create or open a handle, to the object with the name global back,
slash and then the actual name.
Let me show you why.
That actually works.