feat(streamer):add streaming for cast file

[irvingoujAtDevolution]

No description provided.

[github-actions]

Let maintainers know that an action is required on their side

• Add the label release-required Please cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module) when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)

• Add the label release-blocker Follow-up is required before cutting a new release if a follow-up is required before cutting a new release

• Add the label publish-required Please publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc) when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)

• Add the label publish-blocker Follow-up is required before publishing libraries if a follow-up is required before publishing libraries

[CBenoit]

suggestion: The ultimate goal of streaming and shadowing is shared, but the code itself is completely decoupled. What about splitting into two crates?

I suggest these:

• ascii-streamer
• video-streamer or webm-streamer

I think it’s completely fine to remove the Signal trait and to use Arc<Notify> directly.

[CBenoit]

thought: Is it the result of building the NPM package? This should be an artifact that we don’t checkout in the git repository, but instead build when necessary (dev machine or CI).

[irvingoujAtDevolution]

I agree, let me fix that in a separate PR, and I will rebase to that one.

[CBenoit]

question: Do you really need a new trait, or you could work with AsyncWrite? There is an adapter to get map a websocket into a AsyncRead + AsyncWrite object:

devolutions-gateway/devolutions-gateway/src/ws.rs

Line 5 in 0016f78

pub fn websocket_compat(ws: WebSocket) -> impl AsyncRead + AsyncWrite + Unpin + Send + 'static {

[irvingoujAtDevolution]

The client need text specifically, if we send bytes it won't work.