ANN: RTC SDK 1.9g > New Message-based Third-party transports

Triggered by a recent discussion in another thread, new components for using
Message-based Third-party transports have been added to the RealThinClient
SDK, with a ready-to-use set of plugging which allow tunneling of all RTC
communication through NexusDB components (Client and Server).

You can now compile your RTC SDK Server applications as:

1) Stand-alone Server using the HTTP protocol
(using only RTC SDK components)

2) ISAPI Extension for your favorite Web Server (MS IIS, Apache, etc)
(using only RTC SDK components)

3) RTC Server and Client integrated in one app (direct link for easier
testing)
(using only RTC SDK components)

4) Secure Stand-alone Server running over a HTTPS protocol
(using RTC SDK with StreamSec Tools or SecureBlackBox components)

5) RTC Applications running inside a NexusDB Server
(using RTC SDK with NexusDB components)

6) RTC Applications running over UDP, Named Pipes, Mapped Memory files
and other cool transports supported by NexusDB components
(using RTC SDK with NexusDB components)

7) RTC Clients ans Servers running over your own message-based transport.
(using RTC SDK and your transport implementation)

NOTES:
- You need NexusDB components to use NexusDB plug-ins.
- You need StreamSec Tools to use StreamSec Tools SSL plug-ins
- You need SecureBlackBox components to use SBB plug-ins

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


.

Relevant Pages

  • Re: ANN: Cost effective ThinDAC resolution in the works...
    ... ThinDAC and RTC SDK was sold as a closely coupled product, but ordered from 2 different places. ... You must get the exact history behind its being from the people behind it, Dmitry and Danijel, but it has been mentioned several times that Danijel has invested time and money in its development and not the least, customers have bought ThinDAC and RTC SDK on false premisis as they were promised ThinDAC v2. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: ANN: RealThinClient SDK > A Fresh Wind ...
    ... was trying to say was that RTC Portal was the biggest concern to RTC ... RTC SDK is the engine/brain powering RTC Portal. ... Components and Applications built on top of the RTC SDK automatically become part of the RTC SDK familly of Products, because the RTC SDK is a Framework which not only empowers the new components and applications with that communications functionality, but it also defines unified interfaces through which all components based on the RTC SDK interract with each other to make a single combined entity. ... Now imagine what would happen if a number of third-party component vendors would start using the RTC SDK as their preffered way of making components in need of some communications layer. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: POLL: RTC Remote Tools 2.0
    ... The product was called RTC Remote Tools. ... RTC SDK is a completely different product. ... and using RTC SDK is not possible without Video Codec ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: ANN. GranPuente PC remote control library
    ... RTC is not simply a socks library. ... for writing Clients, Servers and ISAPI extensions using the HTTP protocol. ... their code with anything that anyone else has written for the RTC SDK, ... if you want a Messenger Server or a Web Server (which are both ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: OT: Open Source and community support
    ... Danijel Tkalcec, Team RTC ... Even though I think that the RTC SDK is unique in it's ... If giving RTC SDK as Open Source would increase other RTC product ... support from the new Open Source RTC SDK community, ...
    (borland.public.delphi.thirdpartytools.general)