Skip to content

feat: 增加 GEM 通讯建立策略 - #24

Merged
CSJ608 merged 1 commit into
mainfrom
feat-communication-establishment-policy
Aug 29, 2026
Merged

CSJ608 merged 1 commit into
mainfrom
feat-communication-establishment-policy

Conversation

@CSJ608

@CSJ608 CSJ608 commented Aug 29, 2026

Copy link
Copy Markdown
Owner

变更

  • 为 GemHostServices 与 GemEquipmentServices 增加单一、精确可释放的通讯建立应用策略,处理器接收请求方 GemIdentity。
  • 未注册策略时保持自动接受;策略拒绝时返回 profile 失败应答与空身份 List,发起方收到 GemRequestRejectedException。
  • 拒绝首次建立不会进入 Communicating;拒绝已通讯状态下的重新建立不会覆盖既有 CommunicationState 或 PeerIdentity。
  • 应用改变策略后可在同一 Selected 会话显式重试;本切片不增加自动重试、计时器或后台恢复循环。
  • 更新 README、GEM 行为文档、端点角色、标准边界、路线图与 CHANGELOG。

验证

  • dotnet build SecsFrame.slnx -c Release
    • 0 警告,0 错误
  • dotnet test SecsFrame.slnx -c Release --no-build
    • SecsFrame.Tests: net8.0/net10.0/net48 各 199/199
    • SecsFrame.Secs4NetInterop.Tests: net8.0/net10.0 各 2/2
    • 互操作项目继续使用 nuget.org 官方 Secs4Net 3.1.0

新增状态测试覆盖 Equipment 拒绝 Host 首次建立后恢复、Host 拒绝 Equipment 重新建立时双方状态/身份保持、同会话重试恢复,以及策略释放后恢复默认自动接受。

标准边界

实现继续以可替换工程 profile 为基线,并记录 SEMI E30-0526 核对边界;不声明完整 GEM 合规。

@CSJ608
CSJ608 merged commit b5102ed into main Aug 29, 2026
4 checks passed
@CSJ608
CSJ608 deleted the feat-communication-establishment-policy branch August 29, 2026 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant