logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-02-17 04:33:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply suggestion from @igor-sirotin

Browse Source 
Co-authored-by: Igor Sirotin <igor.sirotin.1012@gmail.com>
This commit is contained in:
Jazz Turner-Baggs 2026-02-05 17:13:01 -08:00 committed by GitHub
parent 0775ad6e08
commit f07c5b170c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
standards/application/chat-framework.md
View File

@ -113,7 +113,7 @@ The core of an initialization protocol is a defined location and procedure for r
Many chat protocols choose to define the initialization protocol within the conversation protocol. This tight coupling produces two negative artifacts.
- New conversation protocols must define and deploy there own initialization channels. Increasing overhead and adding complexity.
- New protocol upgrades then create partitions in the communication network, as older clients have no means of communicating with new clients.
- Protocol upgrades then create partitions in the communication network, as older clients have no means of communicating with new clients.
Separating channel initialization from conversation flow allows multiple conversations to reuse the same initialization channel. This reduces effort for new conversation protocols, and is especially valuable when upgrading existing ones. Being independent the initialization pathway can persist across conversation versions. Even if an older client cannot parse new message types, it can still recognize their presence, adding observability.