-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5391 from FederatedAI/feature-2.0.0-rc-release-note
add release note
- Loading branch information
Showing
1 changed file
with
24 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,25 @@ | ||
# Release 1.0.0-alpha | ||
# Release 1.0.0 | ||
## Major Features and Improvements | ||
* Support grpc synchronous transmission and streaming transmission. Compatible with eggroll interface and can replace FATE1. x rollsite component | ||
* Support asynchronous message transmission, which can replace rabbitmq and pulsar components in FATE1. x | ||
* Support HTTP1. X protocol transmission | ||
* Support cluster deployment and inter-site traffic control | ||
* Support networking as an Exchange component | ||
|
||
|
||
* Implement the transmission interface in accordance with the “ Technical Specification for Financial Industry Privacy Computing Interconnection Platform”,The transmission interface is compatible with FATE1. X version and FATE2. X version | ||
|
||
* Supports GRPC synchronous and streaming transmission, supports TLS secure transmission protocol, and is compatible with FATE1. X rollsite components | ||
|
||
* Supports Http1. X protocol transmission and TLS secure transmission protocol | ||
|
||
* Support message queue mode transmission, used to replace rabbitmq and pulsar components in FATE1. X | ||
|
||
* Supports Eggroll and Spark computing engines | ||
|
||
* Supports networking as an Exchange component, with support for FATE1. X and FATE2. X access | ||
|
||
* Compared to the rollsite component, it improves the exception handling logic during transmission and provides more accurate log output for quickly locating exceptions. | ||
|
||
* The routing configuration is basically consistent with the original rollsite, reducing the difficulty of porting | ||
|
||
* Supports HTTP interface modification of routing tables and provides simple permission verification | ||
|
||
* Improved network connection management logic, reduced connection leakage risk, and improved transmission efficiency | ||
|
||
* Using different ports to handle access requests both inside and outside the cluster, facilitating the adoption of different security policies for different ports |