8:52 they call a Magazine a Clip, even though we haven't used clips since ww2 with the M1. I find it absolutely fascinating that people still consistently make this mistake, when it should be common knowledge what the difference between a magazine and a clip is.
@@jytvreal But where can I find ready-made programming projects to see the functions and basics I learned, so I can understand when to use them in C++?
I tried implementing SSE on my website, with Next.js as the client and Express.js as the server. It worked smoothly locally, but when I deployed it on GCP, it didn't function correctly. The server was able to send messages, but the client wasn't able to receive them. Can you help me understand why this isn't working?
One small tweak to thinking about the latency of Microservices - They are communicating (hopefully) over an intranet, not the internet. The problem with 3rd party APIs (like, say, using Google for Oauth) is that you have to traverse the internet to access it. To be clear about what I'm saying, here's an example: Accessing data from a microservice is like going to your neighbor's house in the same neighborhood (within a specific distance, like 1/4 of a mile, let's say). Accessing data from a 3rd party service, like Google Oauth, is like having to get on the highway. One is much less busy and a much shorter route while the other is a much longer route and potentially packed with traffic. Not saying that there is no latency with an intranet, but it's negligible compared to 3rd party services.
unless you need duplex, forget about sockets.. sse is way simpler and less demanding on networks and servers.. actually, I was struggling to get socketio app to run on azure app service, then this video reminded me about SSE, which I completely forgot, even though I have been working with signalr for a decade.. nodejs+sse is all anyone really needs.. there is no real need to push messages from client to server, they already have a tech for that, its called REST. One more thing, sockets doesnt support auth headers, which means you have to pass the JWT in the QS. This is a serious security vulnerability, no matter what the "experts" say.. SSE, you can pass the JWT right in the Auth header.. and thank you my friend for pulling me out of the endless loop of docker, azure, app services, bla bla bla
im pretty new to coding but after playing the PC ports of these old GTA games, is it even worth looking at the source code still? they wouldnt really meet up with todays standards.
One needs -a server endoint -them headers -a while loop running on the endpoint. -inside the loop an async function that awaits for your viewmodel (body) task to be complete. -a singleton SseService. -a private constructor with inside of it a subscription to a home made server side event. -a function that triggers the event. -a SemaphoreSlim or a TaskCompletionSource to handle concurrent acces. Hallelujah !!! Oh and the event source in Javascript (the endpoint ) to update da client ui with your beautiful viewmodel of course. And to close the event source in the beforeupload event (also js) 😅
I wish my college professors gave us real life examples like this!! They taught us inheritance, class, object etc but never really taught us how they are implemented in the real world.
Thank you very much, I did lost an amazing job opportunity because I could not explain exactly it. You did it sou clearly that next time I will no fail 😅
at this point rockstar should just release code for their really old games (before gta 4), nobody pays for them anymore, everyone owns a pirated copy for pc and anyone can pirate them for old consoles... Many people even have revere engineered code for many of their games (or even original code for gta 5), I can't imagine that releasing gta sa code for example would hurt sales of san andreas, since nobody bought that game in the last 10 years lol
