Author: AlexAlex Date: Apr 16, 2008 00:27
Sten Westerback (MVP SDK 2005-6 :) wrote:
>
> The correct API to use is called Win32 API ;)
The Misc API might be interested too however (given you referred to the
cross posting ;))
> I would suggest you use http(s) from communication unless you want to make
> life easier and use a named pipe with it's built-in authetication (asuming
> you have a domain).
Well, to be honest I am not having such a big experience with named
pipes so I would likely go with IP (whether UDP or TCP and if TCP
subsequently HTTP is yet to be decided), aside that I suppose it could
be problematic via Internet connections.
> A desktop is needed so the working thread(s) of processes started have
> something to draw on (or at least a console if that's all you need).
Sure, my initial concern was that the desktop/session isolation wouldnt
really be given by using the "regular" calls, which doesnt seem to be
the case with Terminal Services.
This appears of having been confirmed by several responses to the same
question in microsoft.public.win32.programmer.kernel.
|