Client to Server Streaming

[exxoscott]

Hello,

I am sorry if this is obvious to the highly skilled, of which I am not. I am also sorry if this is not the most appropriate place to ask this.

We are using signalR in a React front-end to stream data from the client to the server, and that works nicely - in working on the native iOS app, and with this wrapper specifically, I am not entirely sure how to do the same. In the JS client library, you create a Subject object and pass it as an argument to in a connection.send() call, then you call .next() on the subject object to stream chunks of data across.

I cannot find an equivalent with this library, and it seems the .stream call is intended for server to client streaming as best I can tell.

Might this be possible with SignalR-Client-Swift?

Thanks.

-Scott

[moozzyk]

Unfortunately, client-to-server streaming is currently not supported by this client.

[kcrandall]

@moozzyk would you be able to add this if we sponored you on a contract basis?

[moozzyk]

Yeah, I would look into it. From what I remember when I investigated it before, it was a decent chunk of work but because the demand was low I postponed it.

[kcrandall]

Ok great thanks, ya we are doing some audio streaming in our application so this is very useful. If you could send a quote on what you think would be reasonable to keston@meetrobin.app (USD preferably)

[moozzyk]

Sounds good. You can expect to hear from me by end of this week.

[moozzyk]

A very rough but working prototype: 8519acb

[kcrandall]

Wow looks great! Would it also work with a streaming response in the same method? This is the hub method we wanted to use. Stream mic data in and then stream audio text-to-speech data back.

public async IAsyncEnumerable<SpeechStreamingResponse> StreamMicAudioData(IAsyncEnumerable<byte[]> audioStream, int sampleRate)

[moozzyk]

I checked the .NET Client and it does support server streams for the send, invoke and stream methods so there doesn't seem to be any reason to not do this in this client as well. I prototyped with send because it was the simplest and what the docs showed. I might limit the number of streams in the convenience API though.