Board index » delphi » Re: POLL: RTC Remote Tools 2.0

Re: POLL: RTC Remote Tools 2.0


2007-02-09 07:08:06 AM
delphi28
"edbored" writes:
Quote
I want it embedded into the application - nothing else to install or
configure.

I'd prefer component I can drop on a form...
Unless you want to limit the control to your application only, and lose
control of the PC if the application should be "freezed" or crash, it is
better if your application would call an external "tool" when you want to
control the PC where the application is running.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 
 

Re: POLL: RTC Remote Tools 2.0

"Danijel Tkalcec [RTC]" <XXXX@XXXXX.COM>writes
Quote
"edbored" writes:

The product was called RTC Remote Tools.
There was no "SDK" in the name.
(of course - I am tired and hungry - too lazy to look it up)
Quote
You have mixed up everything.
(sorry - I guess I glossed over too many of the postings)
Quote

So, you CAN use the RTC SDK on it is own. You can write complete Clients,
Servers and ISAPI extensions by using ONLY the RTC SDK. If you would like
to
order the RTC SDK, you can always find it here:
www.realthinclient.com/order_sdk.htm
Actually, I have already bought a license...
Quote

You would also need the RTC SDK to compile Video Codec.

>- which also will
>not be released (without WebScript - is that true?).

Am I really so misleading? RTC SDK is the base for everything related to
RTC
(RealThinClient components). All other RTC products (RTC Remote Tools, RTC
Video Codec, RTC WebScript, RTC DAC, etc) are being built to extend the
RTC
SDK and there will be a lot more products released - which will be using
the
RTC SDK.
Misleading - no.
Unclear - yes (but maybe I should come back after I eat).
I understand that RTC SDK is ALSO needed.
To clear things up, once RTC WebScript is completed and
available:
1) will RTC Video Codec be available as a separate (source) product?
2) will an example of using RTC SDK + RTC Video Codec as an embedded
"remote support" tool be available?
Quote

>I was pretty e{*word*277}d about being able to embed remote support IN THE
>APPLICATION. At this point I am starting to get a bit of a bad feeling
>about the whole afair.

Is this what you mean by "remote support"?
www.realthinclient.com/about_rt.htm
No. I can do that now with VNC, Remote Assist, XP Remote Assist,
and a bunch of other stuff. I want it "built-in" to my application.
Thanks for follow-up.
EdB
 

Re: POLL: RTC Remote Tools 2.0

"Danijel Tkalcec [RTC]" <XXXX@XXXXX.COM>writes
Quote
Just to avoid confusion:

1) RTC SDK is a set of components for writing Clients, Servers and ISAPI
extensions.

Here is more info about the RTC SDK:
www.realthinclient.com/about_sdk.htm

RTC SDK can be ordered here:
www.realthinclient.com/

2) RTC Remote Tools is a remote desktop control/support solution
comparable
to PcAnywhere, RemAdmin, VNC, GoToMyPC, which is currently available as
freeware in executable form, but *was* offered with full source code to
Delphi developers who wanted to add remote customer support options into
their Delphi applications. RTC Remote Tools 2.0 is what this thread is
about. For more info about RTC Remote Tools, visit:
www.realthinclient.com/about_rt.htm

When you announced the change moving to RTC Remote Tools 2.0,
was there any indication that source would not be available? I was
under the impression that it was a rewrite, and that it was planned
as a source code product (as, for example, the RTC SDK). I never
got the impression that it was to be an *application*.
EdB
 

Re: POLL: RTC Remote Tools 2.0

"Danijel Tkalcec [RTC]" <XXXX@XXXXX.COM>writes
Quote
"edbored" writes:
>I want it embedded into the application - nothing else to install or
>configure.
>
>I'd prefer component I can drop on a form...

Unless you want to limit the control to your application only, and lose
control of the PC if the application should be "freezed" or crash, it is
better if your application would call an external "tool" when you want to
control the PC where the application is running.
My applications never freeze or crash.
<g>
That's a fair point. It is extremely rare for them to freeze, and
so far every time it has happened it was related to something
wonky in the OS - I would have to do full desktop 'remoting'. I
can already do that with a variety of tools.
EdB
 

Re: POLL: RTC Remote Tools 2.0

"edbored" writes:
Quote
(but maybe I should come back after I eat).
LOL! Ok, you have been forgiven ;)
Quote
To clear things up, once RTC WebScript is completed and
available:
To clear things up: RTC WebScript is an add-on to the RTC SDK which allows
the use of scripted HTML files to write Web Applications. It has nothing to
do with RTC Video Codec or RTC Remot Tools.
Quote
1) will RTC Video Codec be available as a separate (source) product?
Will need to think about this.
Quote
2) will an example of using RTC SDK + RTC Video Codec as an embedded
"remote support" tool be available?
Yes, but only one *very* basic example, where the Remote Host (what usually
your customers would use) will be listening on a Port and acting as a
Server, accepting incoming connections from any Remote Control/Viewer
application (what you would usually need), allowing any Remote
Control/Viewer to take control of the Host PC. No Gateway, no
authentication, no options to connect "the other way around". This would be
a plain and simple example in case the Host (PC you want to control) has an
open port and allows any Remote Control to take over it is desktop.
I would NOT recommend that someone takes this example and extends it, since
you will more than likely need the connection to go "the other way arround",
but - as Tony said - it will be better than nothing.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 

Re: POLL: RTC Remote Tools 2.0

"edbored" writes:
Quote
That's a fair point. It is extremely rare for them to freeze, and
so far every time it has happened it was related to something
wonky in the OS - I would have to do full desktop 'remoting'. I
can already do that with a variety of tools.
Ok. Just wanted to make sure you understand the risks.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 

Re: POLL: RTC Remote Tools 2.0

"Danijel Tkalcec [RTC]" <XXXX@XXXXX.COM>writes
Quote
"edbored" writes:
>(but maybe I should come back after I eat).

LOL! Ok, you have been forgiven ;)
Just came back from supper... <g>

>To clear things up, once RTC WebScript is completed and
>available:

To clear things up: RTC WebScript is an add-on to the RTC SDK which allows
the use of scripted HTML files to write Web Applications. It has nothing
to
do with RTC Video Codec or RTC Remot Tools.
My bad - my impression was that evey time someone mentioned "video
codec" you countered with "after WebScript" - just trying to figure out
the relationship (evidently no more than a development scheduling issue).
Quote
>1) will RTC Video Codec be available as a separate (source) product?

Will need to think about this.

>2) will an example of using RTC SDK + RTC Video Codec as an embedded
>"remote support" tool be available?

Yes, but only one *very* basic example, where the Remote Host (what
usually
your customers would use) will be listening on a Port and acting as a
Server, accepting incoming connections from any Remote Control/Viewer
application (what you would usually need), allowing any Remote
Control/Viewer to take control of the Host PC. No Gateway, no
authentication, no options to connect "the other way around". This would
be
a plain and simple example in case the Host (PC you want to control) has
an
open port and allows any Remote Control to take over it is desktop.
Right - that kills it for me anyway. I am not interested in trying to
explain to a client why I want them to open an incoming port...
Quote
I would NOT recommend that someone takes this example and extends it,
since
you will more than likely need the connection to go "the other way
arround",
but - as Tony said - it will be better than nothing.
Tony's clients must be less paranoid than mine. <g>
If I am now going to accept that I need to shell out to 'remoting tool',
my first attempt might be to use UVNC SingleClick. I can create the
helpdesk template on the fly, then call the exe with various parameters.
There's encryption available, and the ability to set up a network
repeater where both ends of connection dial out.
Getting back to the original question - in trying to determine what
model you should use for distribution, you will need to address what
benefit your portal product will provide over what I can build
from UVNC and SC.
EdB
 

Re: POLL: RTC Remote Tools 2.0

"edbored" writes:
Quote
When you announced the change moving to RTC Remote Tools 2.0,
was there any indication that source would not be available?
No.
Quote
I was
under the impression that it was a rewrite, and that it was planned
as a source code product (as, for example, the RTC SDK). I never
got the impression that it was to be an *application*.
1) My plan was to implement SOAP support for RTC SDK remote functions, but
after doing more research, I have changed this to XML-RPC, because it fit
better to the flexibility of RTC remote functions than SOAP.
2) My plan was to have RTC WebForms, RTC Remote Tools 2.0 and RTC Database
finished about a year ago. For each of these 3 add-ons, I had a more-or-less
dedicated developer. Remote Tools developer quit after 2 months, RTC
Database developer found a job and quit after 4 months, RTC WebForms
developer was making promises for about 10 months, then he also quit without
having done anything. Some of these developers even got a nice paycheck from
me, which I had to "write off" as a loss.
3) My plan was to have RTC SDK for Linux and .NET before December 2006, but
there was either too many other things to do, or too much distraction from
things that didn't work, so everything stalled. I would say, I wasn't focused
enough, working on everything and nothing.
4) One of my biggest plans in life was to write the best Accounting software
for the Croatian market, but even though I had written the best Accounting
software for the Croatian market in Delphi for Windows, since I had a bad
marketing and financial strategy, I wasn't even able to make enough income
to live off my earnings, but my competitors were filling their pockets
selling {*word*99}py DOS applications.
5) Since my plan with that Accounting software didn't work, my next plan was
to go find me a good-paid job in Germany, work for the company 3-5 years and
save as much money as possible, then get back to Croatia and form a team of
developers to continue where I left off. Instead, I met a girl "from home"
living in Frankfurt/Main, we got married 2 years later, now we are living
near Frankfurt/Main, she is working at a Bank and paying for most of out
expenses, so I can work from home and try to build an online business, since
I have no chance to build a local company in Germany from ground up without
any contacts.
6) My plan was also to get a steady income from RTC sales of at least 1.000
EUR/Month before the end of 2006 and that is the only thing which went
according to plan, but ... I didn't think I would manage to make my wife
pregnant. By the amount of time I was spending at the PC, I think it is a
miracle, but it worked and now I need to find a way to triple my monthly
earnings before August 2007, since that is when my wife will start getting
only 60% of her usual paycheck and we will have one more family member to
cloth, feed and worry about.
As situations change, plans change. And my plan is now to focus on the RTC
SDK and components which will add value to the product (like RTC DAC, RTC
WebScript, RTC Functions Wizard, RTC WebForms, Linux and .NET support) while
trying to embark on a new market with a commercial product based on RTC
Remote Tools (RTC Portal). RTC Remote Tools with full source code is simply
not profitable enough, but it would be the main RTC Portal competitor, so I
can't afford to continue selling it.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 

Re: POLL: RTC Remote Tools 2.0

"edbored" writes:
Quote
My bad - my impression was that evey time someone mentioned "video
codec" you countered with "after WebScript" - just trying to figure out
the relationship (evidently no more than a development scheduling issue).
Yep.
Quote
Tony's clients must be less paranoid than mine. <g>
I doubt Tony will be using this example in real life, but it shields me from
giving out my "secrets" about how I want to do the RTC Portal, while still
offering a working remote desktop control example to someone who wants to
write their own solution and not use the RTC Portal applications.
Quote
If I am now going to accept that I need to shell out to 'remoting tool',
my first attempt might be to use UVNC SingleClick. I can create the
helpdesk template on the fly, then call the exe with various parameters.
There's encryption available, and the ability to set up a network
repeater where both ends of connection dial out.
Sounds like you're covered, then.
Quote
Getting back to the original question - in trying to determine what
model you should use for distribution, you will need to address what
benefit your portal product will provide over what I can build
from UVNC and SC.
I will have to get a complete feature list together when the product is
finished, but the most important benefits will probably be:
1) No installation required (single exe Control, single exe Client, single
exe Gateway)
2) HTTP protocol for all communication using automatic compression and data
encryption, working through a HTTP Gateway, so all Clients and Controls can
connect to one another without having to make changes in firewalls or HTTP
proxy servers.
3) Hosted Gateway options for a low subscription fee.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 

Re: POLL: RTC Remote Tools 2.0

Danijel Tkalcec [RTC] writes:
Quote
"edbored" writes:

I doubt Tony will be using this example in real life, but it shields me from
giving out my "secrets" about how I want to do the RTC Portal, while still
offering a working remote desktop control example to someone who wants to
write their own solution and not use the RTC Portal applications.
Yes, I'd only use such a example for learning purposes.
I currently have a help desk application that is installed on 10,000+
PCs that uses VNC server and a Synapse based NT service that starts and
stops a zebadee tunnel and the VNC server only when a help desk tech
takes control, when they are done my Synapse based protocol shuts down
the tunnel and the VNC server. It works well and I have file transfer,
chat etc all implemented via Synapse. it is been in use for over 2 years
without issue, however there is some overhead in using the Zebadee
tunnel that causes slow connect times, especially on lower end PCs.
If I can get rid of VNC and simply use the existing Synapse SSL I would
see a big increase in performance.
I want to be able to take control of a PC and not allow any other
connections while being controlled, so a simple demo is exactly what I
need, I am not interested in a http tunnel or a gateway portal as in my
environment it would never be needed.
Later,
Tony
 

Re: POLL: RTC Remote Tools 2.0

"Danijel Tkalcec [RTC]" <XXXX@XXXXX.COM>writes
Quote
"edbored" writes:
>When you announced the change moving to RTC Remote Tools 2.0,
>was there any indication that source would not be available?

No.

>I was
>under the impression that it was a rewrite, and that it was planned
>as a source code product (as, for example, the RTC SDK). I never
>got the impression that it was to be an *application*.
<snip>
Quote
As situations change, plans change. And my plan is now to focus on the RTC
SDK and components which will add value to the product (like RTC DAC, RTC
WebScript, RTC Functions Wizard, RTC WebForms, Linux and .NET support)
while
trying to embark on a new market with a commercial product based on RTC
Remote Tools (RTC Portal). RTC Remote Tools with full source code is
simply
not profitable enough, but it would be the main RTC Portal competitor, so
I
can't afford to continue selling it.
Thank you for the detailed (and personal) information - given this history,
I understand exactly why we're at this perceived (by me) 'crossroads'.
I withdraw anything I said that might have annoyed or upset you -
do what you need to do to keep RTC SDK viable and moving along.
I'm not sure if Portal will work for me (and, as I said, there are
certainly many low cost competitors out there already), but many
of the other products on your plan are of interest.
May your wife and child continue to be so understanding!
Cheers,
EdB
 

Re: POLL: RTC Remote Tools 2.0

"Tony Caduto" <XXXX@XXXXX.COM>writes
Quote
I currently have a help desk application that is installed on 10,000+
PCs that uses VNC server and a Synapse based NT service that starts and
stops a zebadee tunnel and the VNC server only when a help desk tech
takes control, when they are done my Synapse based protocol shuts down
the tunnel and the VNC server. It works well and I have file transfer,
chat etc all implemented via Synapse. it is been in use for over 2 years
without issue, however there is some overhead in using the Zebadee
tunnel that causes slow connect times, especially on lower end PCs.
If I can get rid of VNC and simply use the existing Synapse SSL I would
see a big increase in performance.
Is any part of that "publishable" - that is, could you provide more
detail of how you go about using Synapse and Zebedee? Not code
level, just a desription that mightsave someone time in trying to
produce a similar setup.
Cheers,
EdB
 

Re: POLL: RTC Remote Tools 2.0

"edbored" writes:
Quote
Thank you for the detailed (and personal) information - given this
history,
I understand exactly why we're at this perceived (by me) 'crossroads'.
I withdraw anything I said that might have annoyed or upset you -
do what you need to do to keep RTC SDK viable and moving along.
Thank you for your understanding.
Quote
I'm not sure if Portal will work for me (and, as I said, there are
certainly many low cost competitors out there already),
No problem. As long as there is an alternative,
I don't need to feel guilty for not offering Remote Tools source code.
Quote
but many
of the other products on your plan are of interest.
That's great!
Quote
May your wife and child continue to be so understanding!
Thanks!
I have a feeling my wife is "tolerating" me for now, but if my plans with
RTC don't work out, I will have no other option but to find a dayjob and
work on RTC in my spare time - of which I doubt much would be left, so ...
I'd better not think about this alternative.
Focus is the key :o)
And now I got to go to bed (it's past 5:30 AM - I am on GMT+1).
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
 

Re: POLL: RTC Remote Tools 2.0

edbored writes:
Quote
Is any part of that "publishable" - that is, could you provide more
detail of how you go about using Synapse and Zebedee? Not code
level, just a desription that mightsave someone time in trying to
produce a similar setup.

Cheers,
EdB


Well, lets just say I created my own protocol using Synapse and I fire
up the tunnel using createprocess, I then test the viability of the
tunnel and if I can connect I then fire up the VNC server using it's
command line options and set the server to accept connections only from
localhost i.e. the tunnel. ON the client I fire up the tunnel and the
VNC viewer from a thread and use waitforsingleobject, so I know when the
viewer has closed, then I send a signal to the remote service to
shutdown the tunnel and the VNC server. It all works great and because
I am running the VNC server from the context of the service the
CTRL+ALT+DELETE still works :-)
I store the PID of the zebadee tunnel and use that to kill it when the
signal comes from the Synapse Viewer application. I shut the server
down by calling the VNC server exe again with the shutdown command line
option. I also do some things to manipulate the VNC registry settings
for the password etc.
The security guys are happy with it because it does not leave any VNC
processes running and I bypass the VNC password and use Active Directory
authentication.
I could make it a ton better if I embedded a native remote control
solution that could just go over the existing Synapse SSL connection
used for the start/stop signals and chat.
I also have a Synapse SSH tunnel example on my site, which could be
adapted to a SSL tunnel pretty easily:
www.amsoftwaredesign.com/downloads/synapse_ssh_test.zip
Later,
--
Tony Caduto
AM Software Design
Home of Lightning Admin for PostgreSQL and MySQL
www.amsoftwaredesign.com
 

Re: POLL: RTC Remote Tools 2.0

Danijel Tkalcec [RTC] writes:
Quote
I would NOT recommend that someone takes this example and extends it, since
you will more than likely need the connection to go "the other way arround",
but - as Tony said - it will be better than nothing.
If you did the example I'd be happy with my upgrade I did last year
:-) You have to understand many of us just don't have the time to dig
through the 1.6 source on how to figure this all out so a simple example
of doing remote control with the encoder/decoder library would go a long
way :-)
Later,
--
Tony Caduto
AM Software Design
Home of Lightning Admin for PostgreSQL and MySQL
www.amsoftwaredesign.com