We all love design patterns, and we all wonder when it's best to use them, I'm going to use one of them to apply one business case that you might...
For further actions, you may consider blocking this person and/or reporting abuse
It's a good breakdown, but I find some issues with it.
It has some bells and whistles, eg. you didn't really need to add the database though it's a nice touch, but it is missing the important bells and whistles, like HTTPS instead of HTTP [setting up an ssl with LetsEncrypt is pretty easy these days], also validating the data sent to your server, and logs for catching bots/anyone trying to abuse it, and also how do you validate communications are not being intercepted.
All in all you did a pretty good explanation and showed how server and client side are connected. This part always confuses newbies.
Granted some of these items require longer discussions and your tutorial is already quite long, they at least deserve to be mentioned, AT THE LEAST, HTTPS since SSL/TLS is a requirement not a luxury nowadays.
Thanks for notifying me, I will look further in these topics and might post another one focusing on those items
I would argue that SSL/TLS is not required for the scope of this tutorial. There are plenty other ones that show you how to add it to your nodejs application or using a proxy to do so.
Newbies don't know this. It should at least mention it and use an SSL secured url by the end. HTTPS is vital [mainly because you don't get that fancy lock icon and clients go apeshit if you don't have that lol], but in all seriousness it's not something that should be overlooked. At least link to another tutorial that shows how to do it for this specific stack since that can vary too.
thanks man it helps a lot
A really nice straighton example without bells and whistles.
Just the way i like it. Great work!
Thanks, It really means alot
Beautiful. I have created whole end to end application for truuth.id for their Liveness product.
I have used socket.io in both front end JS and back end with Python Flask. AWS Lambda, ECS, Farget, ALB and some more tools.
Perfectly working. Only glitches is AWS Socket API gateway does not support socket.io yet. As socket.io use both socket and http connection to make full duplex channel for stream and messages.
Any way will try your nodejs based this tutorial as well.
Wish you all the best. Thanks
clear and easy
Thanks for saying that :)
a good idea, but if my backend use another lanuage, how to do
it depends, some other frameworks like .NET uses SignalR, but I prefer Socket.io, any ways how to set it up will be very similar, just syntax differences but not concepts
Please share GitHub link
you can clone from here:
github.com/omar-diaa-48/real-time-...
github.com/omar-diaa-48/real-time-...
Great
Thanks
I think it is great. Simple. For people that are relatively senior (like me) that know node and express and react well and simply want to know/see socket-io in the mix. Great.
Thanks for the article 👌
I thought in new version of socket.io we do not need to define the transport layer to be polling I guess, please correct me If I m wrong, because I saw the query params have the transport polling by default.
you can set it from the client to match the server, or change what the server is waiting for which is the default, I need to investigate the major differences between them, but I couldn't find much difference.
Hi, I need help for the last section of using postman to make a post to the server on port 5000 to add an order. What is the HTTP link I need to use in postman and how is the JSON object structured to POST?
Nice! Thanks for putting this out. You can also set the language for the code for better markdown code formatting
Sure, thanks for telling me
Awesome, thanks for sharing!
Thanks!!
Where can we use this api?
If you clone the 2 repos, you can run both apps and you should be able to use it, you can set what client can be connected to the server in the
originfield when declaring theioobject.