jetty/jetty.project

Jetty 12 - Add a WebSocket MessageSink for Flow.Publisher

Open

#9,722 建立於 2023年5月2日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Java (3,701 star) (1,913 fork)batch import
EnhancementHelp Wanted

描述

Jetty version(s) 12+

Enhancement Description As we have MessageSink for InputStream, we could have an implementation for Flow.Publisher<ByteBuffer> since we cannot directly have Content.Source due to classloading issues.

@WebSocket
public class WSEndpoint {
  @OnWebSocketMessage
  public void onMessage(Flow.Publisher<ByteBuffer> publisher) {
    // Consume the message asynchronously.
  }
}

貢獻者指南

技術棧
java
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java 17+Jetty WebSocket APIReactive Streams (Flow.Publisher)
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
This issue requests adding a WebSocket MessageSink implementation that accepts a Flow.Publisher<ByteBuffer>, similar to the existing MessageSink for InputStream. The challenge is classloading issues preventing direct use of Content.Source. The implementation should be placed in the Jetty WebSocket module (likely under `jetty websocket/websocket core common`). Review the existing `InputStreamMessageSink` as a template. The new class should implement `MessageSink` and handle subscription to the publisher. There are no linked PRs or assignees, so this is open for contribution.