"Dean Hill" schrieb:
Quote
Danijel Tkalcec writes:
>"Dean Hill" schrieb:
>>It's RTC Portal that is my biggest concern.
>
><snip snip snip>
Apologies, reading my sentence back it did not come out right. What I
was trying to say was that RTC Portal was the biggest concern to RTC
SDK as that is the product that is doing well.
Sorry, but what you are saying simply makes no sense.
90% of RTC Portal functionality *is* the RTC SDK.
RTC SDK is the engine/brain powering RTC Portal.
If it wasn't for the RTC SDK, there would be no 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. The RTC SDK is enforcing this synergy effect by
it's design.
There are now hundreds of developers World-wide which have created thousands
of applications and components which are running on top of the RTC SDK. Try
to imagine the power this combined set of components and applications would
give you when you can combine them like building blocks to create your next
master project. Every single piece of code based on the HTTP/S components
inside the RTC SDK is already by RTC SDK's design a plug-in component which
can, without any changes in the code, be integrated into any other RTC
SDK-based application, becoming it is integral part.
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. Just like you can now combine visual
components in the Delphi components palette to put that master-app together,
you can combine all components based on the RTC SDK for rapid development of
your communications layer.
The RTC SDK is all about standards. It is using a standardized and very
powerful request/response protocol (HTTP/S) as the base of all
communication, which makes the Web "tick", while enforcing a framework
standardizing the way you do HTTP. And when you implement new connection
providers for the RTC SDK using new low-level transports, working on
different APIs or even a diferent OS, you are virtually porting all
applications and components based on the RTC SDK to make direct use of that
API and run on that new OS.
There is a huge synergy effect in using the RTC SDK as a standardized
communications layer for HTTP/S based components and applications. By making
the components Free for use, once the components spread in the Delphi
community and a lot of developers start seing the power that lies behind it,
I hope there will be a number of third-party component vendors interested in
writing components which would make use of the RTC SDK and thus actively
extend the framework with new functionality.
I know, this doesn't sound like an easy task, but a number of developers
using the RTC SDK have already begun seing the power that lies behind this
framework. And now that the components are Free to use, I expect that a
number of third-party component vendors will start seing he possibilities
that lie in building new components based on the RTC SDK.
Just think about the possibilities.
Best Regards,
Danijel Tkalcec, Team RTC
www.realthinclient.com
