Is Bidirectional working (client to server to client)?
See original GitHub issueHello again,
I’m not a 100% sure that I understand the meaning of “Bidirectional” But in your console client sample, I’ve added
// in the QuicNet.Tests.ConsoleClient.Program.Main
context.OnDataReceived += Context_OnDataReceived;
// in the QuicNet.Tests.ConsoleClient.Program
private static void Context_OnDataReceived(QuicStreamContext obj)
{
Console.WriteLine("Data Received!");
}
I saw that in your server code you send an “Echo!”, and was expecting a way to get the data through the delegate, but for some reason, I’m not getting anything. I’ve traced in the code, and the bytes are sent successfully, but maybe at a lower level, the data is not processed in the client?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
WebSocket: Simultaneous Bi-Directional Client-Server ...
Conclusion. Overall, WebSocket is a new web protocol that can allow real-time communication between the server and client simultaneously.
Read more >bi-directional communication between server and client
Can anybody suggest a javascript/nodejs solution for bi-directional communication between server and client. The application flow will be ...
Read more >Core concepts, architecture and lifecycle
Bidirectional streaming RPCs where both sides send a sequence of messages using a read-write stream. The two streams operate independently, so ...
Read more >HTTPS for bidirectional communication
The "client" (the hardware device) acts as a server when it receives a command by the remote user. But acts as a client...
Read more >Concluded WG BiDirectional or Server-Initiated HTTP (hybi)
The BiDirectional or Server-Initiated HTTP (HyBi) working group defines the WebSocket Protocol, a technology for bidirectional communication between an HTTP ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, I just did a proof of concept while playing with the code in order to understand it better. I’ve added the code if you’re interested.
I found out that if you call the “new QuicStream”, it doesn’t work. When you look at the CreateStream in Connection, it uses “_streams.Add(streamId, stream);”. So maybe QuicStream shouildn’t be available (internal).
Also, I was sure that you could play with the streamID in order to send multiple message using the same connection. But from what I understand, every time you want to do a new “Send”, you need to create a new connection. Am I right?
Thanks
Class QuicClient2
Class Program from client
I was thinking with the current implementation, it doesn’t seem far from a “websocket” implementation in UDP. That’s why I was asking.
Thanks for your reply