Leave a comment, let me know what YOUR favorite networking library is!

What’s wrong with the linux sockets API? It’s actually very logical and clean, I don’t understand how this is any better.

What I like about sockets are the IO Strategy, especially multiplexing, to handle multiple sockets, using select option to select only the sockets that has pending data, and IOCTL where you can check the state of a socket or set a block state to a socket. For socket strategy there is IOStrategy, Async and Multi-threaded, - IO strategy uses a single thread where it selects sockets that have pending data to handle them, - Async uses opens and closes or uses a thread-pool to handle sockets in separate threads, if you have to synchronize data received from the sockets you have to synchronize it manually - Multi-threaded handles sockets in separate threads, in my opinion multi-threaded should be avoided, it is the easiest to handle but the slowest when handling a lot of clients, - There is also an hybrid mode where using IO Strategy in separate threads as socket channels, for example I also wrote 3 layers of abstraction for the socket library in c++, Socket->DataSocket ->Listening and Connection socket, after this I wrote the communication protocol, because send and recv, does not ensure, you will receive the full message, because if the message is too big, it will be broken into chunks or receive part of the next message, especially if you have blocking turned off per socket A good socket library should have options to use their own strategy(IOStrategy, Async, Multi-threaded, etc,) to handle sockets, an easy to use listening and connection socket, also a communication protocol,

Awesome video, that PTSD from the socket API got me looking for alternatives. Thank you very much!

This is sweet. Sockets is fine but I'm already bangin away at some crazy stuff with this API. Thanks L3!

I love this video. Thank you so much. Now i want MORE SOCKET RELATED PROJECTS

I have been using ZMQ for awhile now to build distributed computing software for Manufacturing and Execution Systems and it works really great... can do anything from normal pub sub and req resp patterns to esoteric patterns like radio dish and multi stage compute pipelines. Maybe someday someone can show it working on an ESP32 or similar...

Awesome! Looks promising for embedded devs.

Thanks man, awesome vid. I've just started to use this library to deploy C code directly to a Raspberry Pi robot of mine. it's super useful. Keep Rocking \m/

a week ago i had no experience in c and 2 days later i made a web server hosting a simple api using winsock2 thanks to discovering this channel! i really enjoy your c videos especially!

I tried to use zmq once in the project, but realized that it does not guarantee delivery on its own. I read parts of zmq source and it appears to me that data, which was sent from zmq and is then in OS network buffer, may get lost when TCP connection will break. Zmq will do re-connection for you, but data from OS buffer may never get to the destination. So without implementing some acknowledge protocol over zmq messages I could not be sure that data put to zmq will be actually delivered. I tried to do that and it was like re-implementing TCP in simplified form. Another solution I came up was to listen to socket events (or whatever it was called) and reacting on disconnections in some way.

It would be nice a Demo using libcurl library and then integrates with a json parser library 😉. Great video 🙏

Hi, wouldn't the zsock_destroy function in server.c never be called ? Wouldn't it be better to setup a function whenever a SIGINT is received that destroys the socket and terminate the server ?

It's nice but so basic. Maybe the rest of the library is more advanced, like for example handle multiple streams concurrently (have a context for the underlying socket) or asynchronous networking like select/epoll.

Interesting how zmq have stuff running post main to detect non freed resources. Maybe that's a signal handler or something, will grep for dangling in the source when I have an opportunity. Thanks for the video!

Bro, thanks you!

Happy 100k subs!!!

In my day job (sadly) I do a lot of web development... this seems very familiar. Nice.

Before investing your time in 0MQ, here are a few considerations: * The sockets API is well documented, and underlies all IP based networking software. You'll need to learn it sooner or later. * 0MQ is not a replacement for the sockets API; rather, 0MQ is a pub/sub networking toolkit built on top of the sockets API. * NATS is a similar pub/sub toolkit which is widely used in industry, but with better intrinsic security than OMQ. * If you want to write networking software which is as reliable as possible, you will need to learn how to use non-blocking I/O with a single thread. 0MQ (and NATS) kick this can down the road by using seperate threads under the hood to buffer messages.

I used ~5 years ago zmq for a RADAR-System to transmit processed I/Q-Data to a websocket-server. From there on, the clients received the data via websockets inside the provided web application.

Thanks. Maybe someday it’d be great to do the same thing in sockets, revisit 0mq at the same time… sort of a compare and contrast.

that's cool, but what about performance tradeoff?

I've heard of ZeroMQ but not CZMQ. Is it like a more simplified version? As for my favorite net lib? In C, I'm using the sockets API directly, with Winsock startup/shutdown boilerplate, because I need like raw TCP/UDP a lot of the time. I want to use Rust, but that's where networking gets... complicated, especially with concurrency, which I'm also struggling with, though the channel semantics look promising. The `tokio` crate seems like the go-to, but if you need a program to do expensive calculations as well (ie. a server-side authority game server), that's where it falls short. I was told to use std::net in conjunction with the `rayon` crate in such cases, but concurrency and networking on that scale makes brain soup.

Do you have / are you going to make a video on the Linux Sockets API?

I wish you do a series solving 42 networks school exercises.

This got my attention 😮😮

at first looking at the title I thought this man was gonna interface the network card directly

cool but what if we need to serve 1000 clients asynchronously? maybe io_uring (liburing) will help?

👍Thanks.

Can you please make a full tutorial on making a C http server for beginners

Spent all day trying to compile ZeroMQ in Visual Studio 2019 with its C++ binding. Learned I've to move on and find something else. Maybe I can compile its C binding on Linux and use the generated library back on Visual Studio (Windows)? Don't want to lose more hours. Also, couldn't find an understandable example of how to implement async named pipes on Windows with C++.

Nahh, I’ll just stick to sockets, plus it’s not doing a lot of abstraction, still bind and connect, what if u wanna use UDP instead of TCP !! though I really loved the way how it giving a warning about the not freed socket.

<a href="#" class="seekto" data-time="6">0:06</a> I do actually have a C networking assisgnment right now :D

If you are running it for sometimes, A client sends a request then crash, Rerunning the client may have a sync issue! How to deal with that situation? A server is sending a message but no client to read, and the new client is sending a message server is busy

This is messaging middle-ware and not network programming. They are different users completely. And not just an abstraction. Also the TCP/IP network programming API is from UNIX not Linux.

Why didn't localhost work on the server side?

Have you heard about DDS?

Nice.

Zeromq rocks

Didn’t you need to allocate a number of bytes for the returned msg string? You just have char *msg in the server and char *str in the client without allocation. Maybe I’m looking too far into this quick demo but just curious as welll.

LocalHorse Gang checking in here

<a href="#" class="seekto" data-time="40">0:40</a> shrek in the top left corner

very rarely people talk about zeromq

I was HUGE ZMQ fan, but I don't think it's grown as much after the passing of Hintjens, their BDFL. I once re-architected the provisioning system for a cloud backend with ZeroMQ and it was such a perfect fit for a distributed, lock-free concurrency across global data centers. My biggest reason to not use ZeroMQ nowadays is a relative lack of security standards across bindings/libraries, particularly for authN and encryption. It also has relatively weak support for some programming languages, like JavaScript. Still, what's better than zeroMQ for building distributed systems? Nothing as far as I am aware 😅

If you're doing networking in C to learn C, this is good, if you're doing networking in C to learn networking, better use the socket API to handle all the networking yourself and understand it more

cool

<a href="#" class="seekto" data-time="498">8:18</a> it's not C if there isn't at least one segfault

I wish i was smarter so I could understand ZMQ :(

ØMQ is a facade then? It kinda sounds like a Plan9 channel.

Remove `sleep(1);`

Ah yes, all those pesky functions that do the exact thing I want them to. To any students watching: Learn the damn socket api. Don't use this crap. Save higher level abstraction until you learn and understand what happens under the hood.

You forgot an exit after your bind check. Now it will still go into the loop. Ugh the receive call returns a pointer to data?! That is a daft implementation. You would want to pass a point to a data block, Because now you need to free the pointer to the data after everything call. Otherwise when you pass in a data pointer you would just free it after your client is done. This returning of a data pointer is not very C-like.

Tenth view.

Am I first?

why would anyone need some library in network programing. I don't like it.

Localhorse..

onion.

Nice video but It reminds me why I don't like programming in C for networking. Header files, **, * &, free etc

Bro is asking to get hacked.

without sockets, but using socket lib. clickbating

and that's why I don't like c. global namespace everything.

you need to shift your video back a little the slight audio desync is fucking killing me

Dude doesn't know what Ø is

Does this shit work on Zig too?

> networking in c but without all those pesky sockets > so we're going to be using zsock

I sure love binding to tcp://localhorse:5555

You aren't checking that zsock_new isn't returning NULL.