updates.txt

Delphi快速开发Web Server

All components are released from the pool when ISAPI extension is unloaded.

---------------------------------------------------------
* Some bugs have been found and fixes
---------------------------------------------------------

1) Fixed a bug where RTC Client using remote functions, set up to use encryption, 
wouldn't be able to communicate with a RTC Server if AutoSessions was FALSE, 
because the client had expected the Server to return a Session ID, 
even if Server didn't want to suppot encryption or use Sessions.
This has now been fixed on the client-side by setting an internal "flag" if 
Server didn't return a Session ID and encryption wasn't required (ForceEncryption=False).

2) There was a bug in the new 3rd-party encryption plugin for clients, 
which has prevented data initial handshake from being sent/received. 
This has now been fixed.

---------------------------------------------------------
* StreamSec Tools SSL plug-ins for the RTC SDK
---------------------------------------------------------

Plug-in for SSL encryption using StreamSec Tools 2.x 
is now included in the RTC SDK package ("LibPlugins" folder).

You will need StreamSec Tools to compile the plug-ins.
Please contact "StreamSec" if you need a more recent version of the plug-in.

---------------------------------------------------------
* EOF/BOF fix for C++ Builder
---------------------------------------------------------

Renamed EOF and BOF methods in the rtcInfo unit, 
to avoid an error message in creating a .hpp file for C++ Builder.

---------------------------------------------------------
* SSL support using Third-party components
---------------------------------------------------------

RealThinClient SDK 1.9 introduces plug-ins for encryption/decryption and 
comes with a ready-to-use plug-in for StreamSec Tools 2.1 SSL support 
(Client and Server). This means that, in case you have StreamSec Tools 2.1 
and the RealThinClient SDK, you can use the new server plug-in to build 
stand-alone HTTPS (SSL) Servers. Naturaly, you could also use the base plug-in 
class (it's a simple class with only a handfull of methods) to implement your 
own plug-ins for encryption/decryption using any other 3rd-party components/tools.

To "convert" your standard RTC HTTP server into a Secure RTC HTTPS Server, 
you just need to put one or two StreamSec components on your DataModule and 
link them to your rtcHttpServer component through the (new) "CryptPlugin" property.

An example for building a HTTPS Server (or converting an existing HTTP Server 
into a HTTPS Server) is available in the Demos/RTCWebForum folder and ... 
a precompiled Forum Server (exe), using the HTTPS protocol and running on port 443, 
is available from the "Licensed Users :: Download Area" - simply unpack the files and run the exe.

---------------------------------------------------------
* RTC Web Forum Demo added
---------------------------------------------------------

New, relatively complex Demo was added to the RTC SDK: RTC Web Forum.

RTC Forum is avilable as a separate project (RTC_WebForum), and it is compiled 
into the RTC WebServer Demo, to demonstrate the abbility to compile several 
complete RTC projects into a single stand-alone server executable.

RTC Web Forum was built from ground up in less than 8 weeks.
This includes 2 weeks for completing the Web Package Manager Demo, 
which is included in the forum as a "virtual" Forum Section.

---------------------------------------------------------
* RTC Web Package Manager Demo added
---------------------------------------------------------

Added a new Demo to the RTC SDK (Web Package Manager).

RTC Web Package Manager is an example Web Application, where users can log in 
and download the latest content to which they have been granted access for.

Visual design was done using templates (HTML files with place-holders),
so it can be modified without changing application code. 

All planning, coding and design was done in only 2 weeks, by a single Delphi 
developer who had NO prior knowledge of RealThinclient SDK components.

Main requirement for this project was to use only RTC SDK components and things 
that come preinstalled with Delphi. NO other third-party components were used.

---------------------------------------------------------
* RTC Quick-Start Server Lessons added
---------------------------------------------------------

Quick-Start Server Lessons: 1, 2, 2b, 3 and 4 
were added to the QuickStart folder, ready-to-run.

---------------------------------------------------------
* RTC WebServer Update
---------------------------------------------------------

1) Reorganized the RTC WebServer in Pages
2) Added File Extension to Content-Type mappings

Now you can define what the WebServer will send to clients in 
the "Content-Type" header when downloading files, which will avoid 
IE displaying any "unknown" content as "HTML".

---------------------------------------------------------
* RTC SDK 1.8p
---------------------------------------------------------

New functions added to the TRtcDataServer class 
(rtcHttpServer and rtcISAPIServer components), which can be used 
to check the total number of currently open sessions in the Server:
- TotalSessionsCount
- TotalSessionsLockedCount
- TotalSessionsUnLockedCount

---------------------------------------------------------
* RTC SDK 1.8o
---------------------------------------------------------

> rtcParse update by Cord Schneider
"This update fixes a minor bug where the last character of the Source is not returned 
by the Output() function. This bug is only noticable when the Source is set directly 
and not via the LoadFromFile() function."

- Cord Schneider

---------------------------------------------------------
* RTC SDK 1.8n
---------------------------------------------------------

> rtcParse update by Cord Schneider
"This update includes a new property, Silent, which will prevent TRtcParse 
from raising an exception when the user attempts to set the value of a token 
that is not present in the template.

This property is particularly useful for templates that may have optional tokens 
and avoids the need to test for the presence of each token before setting its value. 

For example:

...
  parse.Silent := True;
  parse.Value['title'] := 'A Simple Parser';
  parse.Value['color'] := '#FFFFFF';
  parse.Value['bgcolor'] := '#000000';
  parse.Value['page'] := 'rtcParse';
  parse.Value['does_not_exist'] := 'This token does not exist';
  parse.Value['copyright'] := '(C) Copyright 2005'; ... "

- Cord Schneider

---------------------------------------------------------
* RTC SDK 1.8m
---------------------------------------------------------

> New event: OnDataIn
Added "OnDataIn" event, which will be triggered from the lowest level (same as OnDataOut)
to enable monitoring of bytes received through a connection (raw data).

> OnDataIn & OnDataOut events
Published OnDataIn and OnDataOut events for rtcHttpServer, rtcISAPIServer and rtcHttpClient 
components to enable monitoring of bytes passed through the connection.

OnDataIn and OnDataOut events will be triggered for the connection component, even after they
have been mapped to data processing components like DataProvider, ServerModule, ClientModule.

Those events should ONLY be used for monitoring!
Do not use any Read/Write operations from OnDataIn or OnDataOut events!

---------------------------------------------------------
* RTC SDK 1.8l
---------------------------------------------------------

> rtcParser update by Cord Schneider
"I've made a non-critical modification to rtcParse.pas to provide better 
exception handling and also to fix a rare case where Read_File() would 
not correctly free a file handle if an error occurred while seeking to a new location.

Changes include:

  * added ERtcParse exception class so that users can more easily
    trap TRtcParse-related exceptions

  * added better exception handling in Read_File()

  * Read_File() would not free the file handle if an error occurred
    when seeking to a new location in the file being read

I also noticed a curious thing: the template directory in QuickStart\Delphi_rtcParse2 
should be templates ... somewhere along the line, the 's' got dropped off and the 
demo won't run out-of-the-box."

- Cord Schneider

---------------------------------------------------------
* RTC SDK 1.8k
---------------------------------------------------------

> Garbage collection for the design-time package
Included garbage collection in the RTC SDK design-time package.
This should avoid getting Windows Errors when Delphi closes.

> RTC Messenger Client Demo update
Added "SkipRequests" calls to the Logout function,
to avoid getting into the infinite loop with requests being 
reposted over-and-over-again when Server is not available.

---------------------------------------------------------
* RTC SDK 1.8j
---------------------------------------------------------

> Added {$WARN UNSAFE_CODE/TYPE/CAST OFF} directives
To avoid getting warnings about "unsafe" code when creating new
projects in Delphi 7 and later when using the RTC SDK, 
warnings about "UNSAFE" code are now being deactivated for all RTC SDK 
units by using compiler directives in the "rtcDefs.inc" file.

> Added {$WARN SYMBOL_PLAFORM/DEPRECATED OFF} directives
To avoid getting warnings about platform-dependent and "deprecated" code 
when creating new projects in Delphi 6 and later using the RTC SDK,
warnings about "platform dependent" and "deprecated" code deactivated
by using compiled directives in the "rtcDefs.inc" file.

> Added all units to package files list
To avoid getting warnings about implicit unit import when compiling
the RTC SDK package, all units used in the RTC SDK package are now
defined in the Package file's "Contains" list.

---------------------------------------------------------
* RTC SDK 1.8i
---------------------------------------------------------

> Disconnect/Connect with AutoConenct from inside Event bugfix
Fixed a bug with AutoConnect when Disconnect was called from inside an Event in MultiThreaded mode,
which resulted in connection not being re-established