Re: RTC Remote Tools 2.0

Danijel,

I use your package for one purpose: to support my customers using my
programs. I do not resale the package or any derived source code. It seems
like you may be assuming the worst about your customers, and that will never
work well for your business.

Here is my proposal: (I may have client/server terminology backward here,
assume client=customer's computer)

1. Release all clients with source code: file transfer, chat, desktop. This
would allow easily adding remote control capabilities to any new
applications. It would also allow compiling on new version of Delphi.
2. Release the server only as an executable file. This file could "phone
home" to your server to confirm licensing. I'll leave the details of that to
you and RTC SDK.
3. Maintain a system that will be fast and reliable for the licensing check,
or have it simply default to assume you are legally using the server.

Some nice things that could be included in the componentized package:
1. A remote logging component to send a log message to the server
programmatically. I do this right now by UDP messaging.
2. I would also use this system to log madExcept exception reports, so it
would need to be able to handle large text files. I do this now by using
madExcept email setup.
2. Ability to send a screenshot programmatically. I do this now with an
email component.
3. Built in IM system, so the server can chat easily with multiple clients.
I do this right now using a simple textbox on the remote client computer, as
I could never get the old chat client to work correctly. Of course my
solution ends up with the client and server typing at the same time
occasionally.
4. The server should have a great usage log so you know who you help with
what. This could be accomplished by setting some properties on the client
components to identify customers, such as a customer ID, current user,
station name, IP address, email (nice to quickie email something to them).
5. Reporting would be nice here as well. I think it would be great to be
able to print or email a report to a customer with the results of a "service
call or call(s)".

Please let me know your thoughts on this. I think adding value to the server
will add money to your bottom line. For me it is all about creating a help
desk for my products and this would certainly do that thoroughly.

I am going to also post this to the third-party newsgroup for feedback, as I
do not feel it is flaming in any way or at least was not intended to be.

-Johnnie Norsworthy


.

Relevant Pages

  • Re: Remobjects v KBM
    ... >> client query components) follow from that. ... Then, connections can be created to say SQL Server, Oracle, Interbase and ... can then be created from the abstract dataset definition in 'customers' to ... implicitly - this makes your code not be database connection specific). ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: outlook on server
    ... I make sure my customers understand up front that they are not ... using the server as a workstation is simply out of the question. ... > I have a client I've had for years now who wouldn't do any maintenance. ...
    (microsoft.public.windows.server.sbs)
  • RE: Certificate logon on Unix
    ... I don't know of any package but there is prolly one out there you should ... The good news is that getting fulle client ... and server side authentication is pretty easy so it will work as a quick ... setup your CA and make the root cert Pbk available to everyone. ...
    (Security-Basics)
  • Client disconnecting over a VPN connection
    ... account package which is phisically located on a remote server. ... Windows rlogin client; ...
    (comp.unix.sco.misc)
  • Re: Remobjects v KBM
    ... > can then be created from the abstract dataset definition in 'customers' to ... One on the client side and one on the server side. ... This is possible to setup on each connection pool, to ensure cross database handling easily via the cross database ...
    (borland.public.delphi.thirdpartytools.general)