ANN: RealThinClient SDK 2.16 > The Highest stability for 24/7 Servers
- From: "Danijel Tkalcec" <rtc@xxxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 10:13:18 +0100
Hi, fellow Developers!
It has been a while since I have posted some "general information" about the
RealThinClient SDK components, so please bare with me, if you already know
what you are about to read here :-)
*** RealThinClient components are extremely stable, easy-to-use and
royalty-free components for writing network, web and rich internet
applications. Applications written using the RealThinClient components are
reliable, offer strong encryption and high performance and work flawlessly
from over the Internet (no firewall or proxy problems).
You want to exchange data over the Internet and need a guarantee that nobody
will be able to "read" what you are sending, but you do not want to pay for
expensive certificates? You can the built-in RTC Encryption for remote
functions, offering patent-pending variable-length encryption (2.048 Bit
strong encryption can be enabled by setting a few properties). Naturally,
you can also use the standard SSL encryption over the HTTPS protocol by
utilizing third-party components like StreamSec Tools
(http://www.streamsec.com) or SecureBlackBox (http://www.eldos.com).
You want to make your functions accessible by a third-party using standard
protocols, or need to access third-party applications using standard
protocols? Among the ability to communicate with RTC clients over its own
compact RTC format (using automatic compression and strong encryption),
RealThinClient SDK also offers the ability to write and call remote
functions/procedures using the XML-RPC format
(http://www.google.com/search?q=xml-rpc), offering you an easy way to
communicate with third-party applications.
*** RealThinClient SDK 2.16 components have (again) been stress-tested for
24/7 operation under full Server load, to ensure the highest possible
stability on high-load/demand Servers. In this last test, which is now
running 7 days for 24 hours non-stop, the RTC Server has been put to a
stress-test with a constant load of 600 connections (12 PCs in a 100 MBit
LAN, each using 50 connections) continuously calling remote functions on the
Server, using mixed settings with automatic compression and encryption over
the compact RTC data format and the standard XML-RPC format. All clients
were accessing the same Server and using the same remote functions. RTC
Server has responded to each request using the same format the request came
in: (a) RTC format with/without encryption/compression and (b) the standard
XML-RPC format over HTTP.
During the past 7 days (662.611 seconds), processing speed has been around
3.280 requests per second (over three thousand two hundred results were sent
each second), in which time the RTC Server has received and responded to
over 2.104.262.656 requests (more than 2 billion /maxlongint/ remote
function calls), with memory usage staying around 103 MB, serving 600
connections at all times. This latest test is still running - all 600
connections are still sending remote function calls to the Server and
getting their results. There have been no glitches or problems of any kind.
To see the results from more RTC SDK stress- and load-tests, visit:
http://www.realthinclient.com/tests.htm
Even though some developers would think that the HTTP protocol is a "show
stopper", it really depends on the underlying implementation. As you can
see, the RealThinClient SDK is pretty fast at what it is doing. Check the
results from our test using the compact RTC format, with 5.297 requests per
second when 600 connections are being used "to the max" - comparable to 600
PCs in a LAN accessing the Server.
*** Utilizing the HTTP(S) protocol, there are no problems with firewalls or
proxy servers.
All RTC Servers can be made accessible from all around the World by using
the RTC Clients (RTC SDK includes client- and server-side components),
XML-RPC Clients (Java, C++, PHP, .NET, etc) and/or Web Browsers.
Since the first components release in May 2005, we haven't heard of a single
PC on this globe from where you couldn't access RTC Applications (like the
RTC Messenger). Even the highest-security corporate LANs with the most
rigorous firewall and proxy settings were no problem, so ... we can safely
say that any PC which has access to the Web will be able to access your Web
Applications and/or Rich Internet Applications over the Internet - unless
your domain was deliberately being blocking by the network admin.
*** RealThinClient SDK components are not only stable and reliable, but also
easy to use and very flexible, which is one of the reasons that
RealThinClient SDK is currently being used by hundreds of Delphi and C++
Builder developers all around the World, writing high quality Web
Applications and Rich Internet Applications, running inside corporate LANs
and over the Internet. To see testimonials from licensed RealThinClient SDK
users who have decided to write something about their experience with RTC
components, visit:
http://www.realthinclient.com/powered.htm
For additional information on the latest development at RealThinClient
components, please visit RTC Forums (News, Quick-Start guide, FAQ, Developer
Support, Blogs):
http://www.realthinclient.com/forum
*** We don't only "sell" the components, we are using them on a daily basis.
For example, our http://www.realthinclient.com domain (where all order
processing and customer support is done) is being powered by the RTC
WebServer, running a RTC Forum written in Delphi 7 Pro by using only the
RealThinClient SDK components. The RTC WebServer has been in use to power
RealThinClient domains since February 2005, without any problems.
We are also proud to have been one of the first official Turbo Explorer
mirrors (still mirroring, currently with around 40 GB of files served
daily), helping to spread the free Borland Turbo Explorer editions, with all
Turbo Explorer files made available for download from our RTC WebServer:
http://www.realthinclient.com/borland
If you have any questions about the RealThinClient components, feel free to
contact me directly by E-Mail (info) or use the RTC Forums for developer
support:
http://www.realthinclient.com/contact.htm
Best Regards,
Danijel Tkalcec, Team RTC
http://www.realthinclient.com
.
- Prev by Date: [ANN] paxScript.NET v2.5
- Next by Date: Re: Diagram component for DB models
- Previous by thread: [ANN] paxScript.NET v2.5
- Next by thread: What is the WYSIWYG editor?
- Index(es):
Relevant Pages
|
