Re: POLL: RTC Remote Tools 2.0

"edbored" wrote:
I'm with Tony on this - on basically every point. One of the things I'd
like
to include in my code is "self-help" - essentially allow a guru at one of
my
customers' sites perform remote-support from within their LAN. If the
"guru" can't solve a problem, then the original user could connect with
me.

For this, you don't really need the source code, as long as you can specify
how the Remote Host/Client will look like and you can call the Remote
Host/Client from all of your applications by using ShellExecute or WinExec
(with parameters).

For the user sitting in front of the remote host, a simple notifiction
window which would be minimized to Tray should be enough to notify the user
about the "remote support person" being connected. And when the user wants
to terminate the Session, he would simply click or double-click the tray
icon. To initiate a new session, he would use the options from your
application again, which would call the same external application (using
WinExec or ShellExecute).

The same goes for the Remote Control/Viewer, which you could also see as a
tool for offering support to your customers. If it had a customizable user
interface, you could also temper with it's appearance, so the support people
using it wouldn't need to be confronted with the fact that you didn't write
it.

Having both sides as executables makes it possible for us to use third-party
components and source code. One of the things we already have a commercial
license for is a new screen capture technology, which is using almost 0%
CPU, but will capture all screen changes instantly (even transparent and CMD
windows).

Best Regards,
Danijel Tkalcec, Team RTC
http://www.realthinclient.com


.