updates.txt

Delphi快速开发Web Server

* RTC SDK 2.31
---------------------------------------------------------

1) Added "AccessMode" parameter to Read_File, Write_File and Scan_File functions, so
   you can now choose the mode in which the file should be opened for reading/writing/scanning.

2) Setting asByteStream position to the beginning (Position=0) when receiving streams with remote functions.
   In prior versions, "asByteStream.Position" was at the end of the stream (the stream was just written),
   so you had to set the position to zero by using "asByteStream.Position:=0" before you could read from it.

3) Fixed the rtcFileProvider Demo (used by the RTC WebServer) to work correctly with relative paths.
   From here on, the current EXE folder will be used as a starting folder for all relative paths.

4) Moved the background Thread for Multithreaded Message Handling to the "rtcHWndPool" unit.

5) Using background thread to process Timeout and Reconnect messages for connections in MultiThreaded mode.
   Older implementations were using the Main Thread, so timeouts and reconnects did not work when the Main Thread was busy.

6) Fixed the rtcHttpClient.WriteHeader(Header_Text:string) method for "useProxy=True".

7) Resetting "Response.StatusCode" and "Response.StatusText" with every new request. 
   With older implementations, StatusCode or StatusText could have kept values from the last 
   response if a malformed HTTP response (without a StatusCode and Text) would be received.

8) Included SBB_FileClient, SBB_FileServer and SBB_WebForum Demos with SSL encryption using SecureBlackBox from Eldos.

---------------------------------------------------------
* RTC SDK 2.30
---------------------------------------------------------

1) RTC WebServer 2 TLS Demo extended to work over HTTP and HTTPS by connecting all 
   components to a HTTP and a HTTPS Server components using a TRtcDualDataServerLink.

   This Demo shows you how to create a single Server executable which will serve
   your applicationa and any files using more than one port and protocol.

2) All Help files have been updated.

---------------------------------------------------------
* RTC SDK 2.29 - Fixing SSL support using Third-party components
---------------------------------------------------------

1) Fixed a problem which caused exceptions when using Third-Party Encryption components (SSL).

   The problem with SSL was that the reported "Response.DataOut" on the Server-side, as well
   as the "Request.DataOut" property on the Client-side would not be correct when using the
   new WinSock implementation which was triggering the "DataSent" event before the data was
   really sent out. Now (same as in older RTC SDK versions), the "DataSent" event will only be
   triggered once the data was *really* sent out (or at written to the WinSock buffer).

2) Added a read-only property "Version_SDK" to TRtcConnection components, which 
   will show the current RTC SDK version (now 2.29) in the Delphi IDE.

3) RTC WebServer 2 Demo is now also available in the TLS version (SSL using StreamSec Tools 2).

---------------------------------------------------------
* RTC SDK 2.28 - important fix
---------------------------------------------------------

1) Added one auto-incrementing number to all sent requests when using encryption,
   so that skipped or aborted requests can not "go by unnoticed" on the Server.

   If Client and Server counters should get "out of sync" while using encryption
   (which will happen if connections get dropped while sending or receiving data)
   the Server will reject the "out of sync" request and notify the client by sending 
   him the "Encryption Key Wrong" response, after which the client will re-initialize 
   the encryption handshake (request a new encryption key).

   Because of the additions required in the encryption control mechanism, 
   this version is NOT compatible with RTC SDK 2.27 or older, 
   unless the "compatibility mode" is enabled.

---------------------------------------------------------
* RTC SDK 2.27 - Major update !!! Read before using !!!
---------------------------------------------------------

1) If you need all your new clients and servers to stay compatible with 
   all older RTC clients and servers, even if this means disabling some 
   new features from the latest RTC SDK, you simply need to declare:

   {$DEFINE OldRtcCompatibilityMode}

   By default, this directive is NOT declared and all new features are used.

   If you still have some older clients or servers, please read the 
   description of "compatibility-breaking" features (below) *before* 
   deploying a new RTC Client or RTC Server to an existing network.


2) RTC SDK versions up to 2.04 are expecting all Field names received with
   remote function calls to be in UpperCase. This is not the case with newer
   RTC SDK versions, which allow working with field names using mixed case,
   without internaly converting all field names to uppercase.

   If you are still using Clients or Servers compiled with older RTC SDK
   versions, you have to define a compiler directive ...

   {$DEFINE RtcUpperCaseFieldNames}

   ... for your project, or to make it default for all projects, 
   do it in the "rtcDefs.inc" file sinde RTC SDK's "Lib" folder.

   This will make sure all Field Names will be converted to UpperCase 
   when sent out, so that older clients and servers won't have problems 
   with the client/server compiled with *this* RTC SDK version.

   This directive is NOT enabled by default.


3) RTC Clients compiled with RTC SDK versions *before* 2.27 do NOT send a
   control sum when using RTC functions with encryption, which makes it
   hard for the Server to check if the control key received from the client
   is a valid control key. Starting with RTC SDK 2.27, RTC Clients will be
   sending a control sum value along with each control key, which RTC Servers
   can use to check if the control key is valid and make sure at least the
   end of the request data was decrypted properly.

   But, since this control sum value is not being sent by RTC Clients compiled
   with RTC SDK versions older than 2.27, those clients would NOT work with
   a RTC Server compiled with the latest RTC SDK version expecting this.

   If you have RTC Clients compiled with RTC SDK 2.26 or older and can not 
   port all of them before replacing the Server, you will need to declare 
   a compiler directive ...

   {$DEFINE RtcDoNotCheckCryptControlSums}

   ... for your project, or to make it default for all projects, 
   do it in the "rtcDefs.inc" file in the RTC SDK's "Lib" folder.

   This will disable this new check on the RTC Server (compiled with the laterst 
   RTC SDK version), so that your RTC Server can continue working with older clients, 
   even when compiled with the latest RTC SDK version. 


---------------------------------------------------------
* RTC SDK 2.26
---------------------------------------------------------

1) More optimizations for working with large data structures and/or 
   sending large requests and/or responses using the Write() method.
   - improved class: TRtcHugeString
   - improved class: TRtcFastStrObjList

2) From this version on, TRtcHugeString class is used for all internal buffers (no more "TStringList")

3) Moved TRtcHugeString class to a new "rtcFastStrings.pas" unit

---------------------------------------------------------
* RTC SDK 2.25
---------------------------------------------------------

1) Fixed a bug which causes an Access Violation when using TRtcClientModule.Call(NIL) 
   and the Request was Aborted. The problem was that the ResultAborted event was called 
   on the "assigned" TRtcResult object (parameter to "Call"), while the TRtcResult object was NIL.

---------------------------------------------------------
* RTC SDK 2.24
---------------------------------------------------------

1) Minor fixes and code readability improvements to the new RTC Value objects implementation.

The first implementation used a TStringList and a search tree to store functions, records, datasets and
http header information. This implementation uses a new class, which encapsulates the functionality of 
a TStringList and a search tree, which reduces the probability of getting the 2 lists "out of sync".

---------------------------------------------------------
* RTC SDK 2.23
---------------------------------------------------------

1) Removed Low-level TCP/IP and UDP components from the components palette.

2) Removed Low-Level TCP/IP and UDP Demos from the "Demos" folder.

This is to avoid new RTC SDK users from stumbling across the low-level components and trying 
to use them for writing RTC applications, which is NOT what RTC SDK was designed for. 
The low-level components are still there in the Lib folder, they are just not installed 
on the components palette. Only the higher-level components are now on the components
palette and only higher-level Demos are in the Demos folder.

If you need to implement your own protocol on top of the TCP/IP protocol,
please contact us directly by E-Mail: http://www.realthinclient.com/contact.htm

---------------------------------------------------------
* RTC SDK 2.22
---------------------------------------------------------

1) Fixed a bug with Cookie expiration time in the RTC WebForum Demo, because of which "Logout" didn't always work.

---------------------------------------------------------
* RTC SDK 2.21
---------------------------------------------------------

1) Added the new unit "memStrIntList" to all RTC SDK packages.

2) Fixed a bug in the new HTTP Header handling (introduced with RTC SDK 2.20)

3) Fixed a bug in the rtcISAPIServer when sending files split in chunks (introduced in RTC SDK 2.0 RC 1).

   The problem was that the OnDataSent event wasn't being triggered after data was forwarded to 
   the WebServer, so only the first block was sent out. After that, an exception was raised in the ISAPI,
   since more data was expected to be sent out. This bug was only related to ISAPI extensions which
   would be sending data out in chunks, like the RTC Forum (sending large files from the download area).

   This bug did not affect working with Remote functions or other implementations where the complete response 
   was sent from the "OnDataReceived" event, while OnDataSent event was left unused. Since in 99,9% of all
   ISAPI extension implementations the complete response is being sent directly from the OnDataReceived event,
   it is very likely that nobody would even notice this bug. I've also found it only by chance, while 
   testig the RTC Forum ISAPI (trying out all the features - including file download).

4) ISAPI connection object will now be released from the pool in case of an exception.
   This is necessary to avoid more problems resulting from that same exception, 
   since the connection could be in a "limb" state after the exception was raised.

5) Help files have been regenerated to reflect the changes in the library.

*** !! NOTE !!! ***

If you are still using RTC SDK 1.9 or older, 
read the warning for RTC SDK 2.20 (below) before upgrading.

*******************

---------------------------------------------------------
* RTC SDK 2.20 - beta
---------------------------------------------------------

**** ! WARNING ! ****

Are you still using RTC Clients or Servers compiled with RTC SDK 1.9 (or older)?

Then do NOT upgrade your Server to RTC SDK 2.20 before your clients have been recompiled 
with RTC SDK 2.04 or newer, otherwise your clients will stop working propperly.

Also, do not upgrade your Clients to RTC SDK 2.20 before your Server has been recompiled
with RTC SDK 2.04 or newer, otherwise your Server will stop working propperly.

*********************