the fact that you explained everything line by line is priceless, I'm confindent that you wrote this yourself unlike 99% of the vidoes i come across on youtube seems like most of them don't have clue as to what they are teaching .
Love the video! Thanks for sharing your knowledge. I think it would have been better for the address to have been stored as a variable. This helps with a couple of things, but mostly saving you from re-writing the same string over and over. let address = "127.0.0.1:8080"; let listener = TcpListener::bind(address).expect("Failed to bind to address: {address}"); println!("Server listening on {}", address);
What happens, if the buffer is not large enough to read the whole message from the stream? I tried reading twice and concatenate the results into the string, but it didn’t seem to work…
So, when you see 0; 1024, think of it as a space reserved for 1024 elements. It's like having a box with 1024 slots, ready to store stuff. You know what I mean ? And what type of stuff goes in those slots depends on what you're doing with them.
@@BekBraceI found the answer: "Unsuffixed literal, their types depend on how they are used". So 0 literal retroactively binds to u8 a fine grained type upon buffer use in read().
can you makea vid on how to make your device a priority and if possible involving the use of rustlang if it get uploaded can you please tag me or forward link as a reply
Hi and thank you for this question. So, to prioritize your device using Rust, you can leverage Rust's thread module to set thread priorities through std::thread::Builder. Alternatively, for more granular control, use the libc crate to interact with the operating system API, allowing you to set process or thread priorities directly. Remember to test your application, monitor system behavior, and adjust priorities cautiously to avoid adverse effects on overall system performance and stability. Have I answered your question ?
the fact that you explained everything line by line is priceless, I'm confindent that you wrote this yourself unlike 99% of the vidoes i come across on youtube seems like most of them don't have clue as to what they are teaching .
Thanks so much for these words🙏. Indeed I've written it myself 🙂
5:15 std::io::Read and std::io::Write are traits in the std::io module
Excellently executed tutorial. Blow by blow, line by line. Subscribed.
Thank you so much, Anthony 🙏🙂
this video it's just perfect, I have no words to describe how amazing this is. Thanks a lot and the way you teach these things is just incredible.
Thank you very very much for your kind words ❤️🙏 Your feedback is what pushes me forward to create more and more content | ••• Thank You !!!
This was great, looking forward for the Tokio tutorial!
Wow! very precise and clear.
Thank you
Thank you so much for depth knowledge
I am so glad you enjoyed it
Can you make a video about Tokio please :)
Certainly )) Thanks for suggestion
Amazing video, my friend :)
Thank you very much 🙏🙏🙏
Love the video! Thanks for sharing your knowledge. I think it would have been better for the address to have been stored as a variable. This helps with a couple of things, but mostly saving you from re-writing the same string over and over.
let address = "127.0.0.1:8080";
let listener = TcpListener::bind(address).expect("Failed to bind to address: {address}");
println!("Server listening on {}", address);
Absolutely.
Thanks for the better code snippet.
i am just three days into rust and i will still watch it
Good luck and happy coding
Great video, I have just started with Rust videos on my channel, this really helped me.
Great my friend !
Cool channel by the way, good luck in your journey 😀
can't wait :)
See You :)
amazing content. please continue to rust series
Hey! Thank you so much: More Rust to come!
That's so interesting 😁
Thank you very much 👋☺️
🔥🔥🔥
Thank you 😊😊😊
What happens, if the buffer is not large enough to read the whole message from the stream? I tried reading twice and concatenate the results into the string, but it didn’t seem to work…
What's your terminal setup?
Yo .. check out my video: PowerShell Terminal Setup - all explained there/ peace
What extentions do you use for rust?
just Rust Analyzer
@@BekBrace Thankyou Very much
Anytime 😊
Slam Dunk 🏀
Yeaaaah
Hate to be that guy, but what's your color theme? It looks amazing!
No problem at all, my friend anything you want 🙂 the theme is VIM dark
@@BekBrace Hi, can't find the theme in the Vscode marketplace
When is the next video coming In this series ?
Next Month, there will be a new video in the series, thank you for your patience.
Hi. Isn't [0; 1024] mean 1024 ints? Or the type is being adjusted to u8 after it's use in read()?
So, when you see 0; 1024, think of it as a space reserved for 1024 elements. It's like having a box with 1024 slots, ready to store stuff. You know what I mean ? And what type of stuff goes in those slots depends on what you're doing with them.
@@BekBraceI found the answer: "Unsuffixed literal, their types depend on how they are used". So 0 literal retroactively binds to u8 a fine grained type upon buffer use in read().
Amazing video! What is the font and the color theme that used in the video?
Thank you.
Theme: Bearded Theme Black & Ruby
Font: Caskadiya Cove
@@BekBraceAre you sure? Cause they look way different for me.
Awesome video! May I ask the font name and color theme name? Thanks.
Thank you!
Theme: Bearded Theme Black & Ruby
Font: Caskadiya Cove
How you can handle more than one connection without a loop encapsulating tcp incomming?....
Create separate threads to handle each client
you got your answer already I see
Theme?
Don't remember, sorry
can you makea vid on how to make your device a priority and if possible involving the use of rustlang
if it get uploaded can you please tag me or forward link as a reply
Hi and thank you for this question.
So, to prioritize your device using Rust, you can leverage Rust's thread module to set thread priorities through std::thread::Builder.
Alternatively, for more granular control, use the libc crate to interact with the operating system API, allowing you to set process or thread priorities directly. Remember to test your application, monitor system behavior, and adjust priorities cautiously to avoid adverse effects on overall system performance and stability.
Have I answered your question ?
bruh, you don't need to write "this line" before everyone comment...
@@DEBBAH1907 bruh, you can simply ignore it, bruh