Hi,
I was looking at svcctl.idl in ros. I wonder, where the "Scmr"-prefix comes from? googling for say "ScmrCloseServiceHandle" gives only results from reactos, nothing else.
"CloseServiceHandle" gives lots of results, of course.
Was the prefix choosen arbitrarily and could have well been "Ros" instead?
Elrond
Screamer? ;0D
On 8/11/06, Elrond elrond+reactos.org@samba-tng.org wrote:
Hi,
I was looking at svcctl.idl in ros. I wonder, where the "Scmr"-prefix comes from? googling for say "ScmrCloseServiceHandle" gives only results from reactos, nothing else.
"CloseServiceHandle" gives lots of results, of course.
Was the prefix choosen arbitrarily and could have well been "Ros" instead?
Elrond
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Elrond wrote:
Hi,
I was looking at svcctl.idl in ros. I wonder, where the "Scmr"-prefix comes from? googling for say "ScmrCloseServiceHandle" gives only results from reactos, nothing else.
Service Control Manager Remote Interface
Was the prefix choosen arbitrarily and could have well been "Ros" instead?
I chose this prefix in order to distinguish the remote interface functions from the internal SCM functions and from the public interface to the SCM.
Regards, Eric
On Fri, Aug 11, 2006 at 09:47:52PM +0200, Eric Kohl wrote: [...]
Service Control Manager Remote Interface
I guessed that part.
Was the prefix choosen arbitrarily and could have well been "Ros" instead?
I chose this prefix in order to distinguish the remote interface functions from the internal SCM functions and from the public interface to the SCM.
Okay, so the prefix is arbitrarily choosen for reactos.
In windows all those functions exactly resemble "the internal SCM functions" and "the public interface to the SCM"?
And on windows, they don't have a prefix?
Thanks for your help.
Elrond
Elrond wrote:
On Fri, Aug 11, 2006 at 09:47:52PM +0200, Eric Kohl wrote: [...]
Okay, so the prefix is arbitrarily choosen for reactos.
MS chose the same, probably for the same reasons.
In windows all those functions exactly resemble "the internal SCM functions" and "the public interface to the SCM"?
I don't know about "Exactly", but the model is usually the same.
And on windows, they don't have a prefix?
The prefix is also Scmr. Also used in Lsa (Lsar, IIRC) and other services.
Thanks for your help.
Elrond
Alex Ionescu wrote:
Elrond wrote:
On Fri, Aug 11, 2006 at 09:47:52PM +0200, Eric Kohl wrote: [...]
Okay, so the prefix is arbitrarily choosen for reactos.
MS chose the same, probably for the same reasons.
In windows all those functions exactly resemble "the internal SCM functions" and "the public interface to the SCM"?
I don't know about "Exactly", but the model is usually the same.
And on windows, they don't have a prefix?
The prefix is also Scmr. Also used in Lsa (Lsar, IIRC) and other services.
Thanks for your help.
Elrond _______________________________________________
My bad, Lsar confused me. Correct services flow in NT is
CreateServiceW->RCreateServiceW->[RPC]->Sc* Internal APIs.
So Scmr == R.
On Fri, Aug 11, 2006 at 07:19:30PM -0400, Alex Ionescu wrote: [...]
My bad, Lsar confused me. Correct services flow in NT is
CreateServiceW->RCreateServiceW->[RPC]->Sc* Internal APIs.
So Scmr == R.
My suggestion for svcctl.idl would be something like:
+#define Scmr(fn) Scmr ## fn ... - DWORD ScmrCloseServiceHandle([in] handle_t BindingHandle, + DWORD Scmr(CloseServiceHandle) ([in] handle_t BindingHandle,
That should make it easier to change the prefix. But maybe just overkill.
Just my 2 cent...
Elrond