Skip to content

OpenIM-v3.0.0-alpha.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@cubxxw cubxxw released this 12 Jul 11:54
· 833 commits to main since this release
v3.0.0-alpha.0
de1b970
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version logging for OpenIM

  • when we change the message propagation model from write diffusion to read diffusion, it can bring some advantages. First, the read diffusion model can reduce network load because messages only need to be sent to users who actually need to receive them, rather than broadcasting to all users. This is especially important for group chats as it avoids sending a large number of duplicate messages. 😊

  • By using reflection and generics to simplify RPC and API code, we can reduce redundant template code and make the code more flexible and maintainable. This simplification can also improve development efficiency and reduce the possibility of errors. 😄

  • Standardizing error codes can greatly simplify problem identification and troubleshooting processes. By defining a unified set of error codes, we can quickly locate and resolve potential issues, improving application stability and reliability. 😉

  • Integrating ZooKeeper with gRPC enables service registration and discovery, making service management and maintenance more convenient. By using ZooKeeper as a service registry center, we can easily add, remove, and monitor service states to ensure system availability and resilience. 😃

  • Optimizing WebSocket long connection management can enhance system performance and stability. By effectively managing long-lasting connections, we can reduce server resource consumption and provide a better user experience. 😊

  • Introducing a server-side session model can solve the problem of unsynchronized unread messages in sessions. By tracking and managing the state of each session, we can ensure that users can receive the latest messages when using the application on different devices, avoiding information loss or duplication. 😄

  • Implementing on-demand message loading can solve the latency issue when logging in with a new device. By dynamically loading messages, we can avoid loading a large amount of data at once, which can slow down the login process, thus improving user experience and system responsiveness. 😊

Test branch

release-v3.0.0-alpha.0: https://github.com/OpenIMSDK/Open-IM-Server/tree/release-v3.0.0-alpha.0

CHAGELOG

What's Changed

New Contributors

Full Changelog: https://github.com/OpenIMSDK/Open-IM-Server/commits/v3.0.0-alpha.0

Unreleased

v2.9.0 - 2023-07-04

Reverts

  • update etcd to v3.5.2 (#206)

Pull Requests

  • Merge branch 'tuoyun'

v2.3.3 - 2022-09-18

v2.3.2 - 2022-09-09

v2.3.0-rc2 - 2022-07-29

v2.3.0-rc1 - 2022-07-25

v2.3.0-rc0 - 2022-07-15

v2.2.0 - 2022-07-01

v2.1.0 - 2022-06-17

Pull Requests

  • Merge branch 'tuoyun'
  • Merge branch 'tuoyun'
  • Merge branch 'tuoyun'

v2.0.10 - 2022-05-13

v2.0.9 - 2022-04-29

Reverts

  • update etcd to v3.5.2 (#206)

Pull Requests

v2.0.7 - 2022-04-08

Pull Requests

  • Merge branch 'tuoyun'

v2.0.6 - 2022-04-01

Pull Requests

  • Merge branch 'tuoyun'

v2.0.5 - 2022-03-24

v2.04 - 2022-03-18

v2.0.3 - 2022-03-11

v2.0.2 - 2022-03-04

Pull Requests

  • Merge branch 'tuoyun'
  • Merge branch 'tuoyun'
  • Merge branch 'tuoyun'
  • Merge branch 'tuoyun'

v2.0.1 - 2022-02-25

v2.0.0 - 2022-02-23

v1.0.7 - 2021-12-17

v1.0.6 - 2021-12-10

v1.0.5 - 2021-12-03

v1.0.4 - 2021-11-25

v1.0.3 - 2021-11-12

v1.0.1 - 2021-11-04

v1.0.0 - 2021-10-28

Reverts

  • friend modify
  • update

Contributors

testwill, FGadvancer, and 5 other contributors
Assets 2
Loading