A
Aarno
I have made a simple local timer service to check "c:\request.txt" and if
found then to launch a local application which exename is written on the
file.
If the request is made from the server's command line (copy reguest.txt
\\tsclient\c\reguest.txt) then the local application in question will be
running immediately. There's however a 8-10 second delay if you try to write
the same reguest file directly (open \\tsclient\c\request.txt for output
....) from a application running on the server.
Any idea what's the reason for the delay? In both cases the timer service
will detect the request file immediately and the delay is someway involved
with application loading after local shellExecute command has been given.
-AT
found then to launch a local application which exename is written on the
file.
If the request is made from the server's command line (copy reguest.txt
\\tsclient\c\reguest.txt) then the local application in question will be
running immediately. There's however a 8-10 second delay if you try to write
the same reguest file directly (open \\tsclient\c\request.txt for output
....) from a application running on the server.
Any idea what's the reason for the delay? In both cases the timer service
will detect the request file immediately and the delay is someway involved
with application loading after local shellExecute command has been given.
-AT