Комментарии:
great video, thank you.
ОтветитьThis is an amazing video. Very clear and especially with the history that explaining why we need it, helps me better understand all the confusion I had to the WSGI, NGINX, Apache, and Django. Thanks for creating such a perfect video!
ОтветитьBeautiful explanation. Top notch illustration.
ОтветитьНиштяк объяснил!
ОтветитьThis explanation of WSGI was perfect. Thank you
ОтветитьBrilliant!!! Thank you so much!
ОтветитьThanks; I got it now.
ОтветитьThank you, this was well explained
ОтветитьGreat explanation
ОтветитьGreat video!. For me is very important to learn the historical part always help me to remenber and all now many time has sense.
Ответитьfire video
ОтветитьThis is an excellent video. Great explanation.
Ответить"I forked python interpreter three times" 🌚. Yeah that would go well in a modern day college class 😂 lol
ОтветитьSuper lesson!
ОтветитьVery nice explanation, thank you!
ОтветитьWow .. finally I understood the low level details behind communication between front-end and back-end
ОтветитьVery good.
ОтветитьGreat explaination with a lot of context, thanks a lot for that!
I was reading 2 articles on WSGI before (first 2 hits on google) and none could really get to the bottom of it.
Straight to the point and hard-to-earn understandings from history point of view to way this is done this way. Thank you for sharing valuable information!!!
❤
Thank you. That was a simple and easy to understand explanation. I particularly appreciate the first few minutes that start with explaining the history of web servers and web development. We 21st century engineers get most things for granted!
ОтветитьThank you so much for the explanation 🙏
Ответитьgreat video! subscribed!
ОтветитьAwesome explanation! hope to see next new vedio
ОтветитьGreat video.
Thank you.
Brilliant Explanation. Thanks a lot
ОтветитьThank you for this great tutorial, much appreciated. However, I need extra guidance relative to my situation.
I have built my Python Script on VSCode using Flask Framework. My target is to deploy that Python Script to Apache server without Flask so I can implement thread safe/multi thread/multi process using WSGI as I expect the application will have massive number of users.
What is the way forward for me?
Again, thank you in advance for any suggestion that you may provide.
Hi, thank you for this tutorial. How does it work for ASGI (e.g., daphne)? Is it the same mechanism, or is there something specific, e.g., about the relation between the proxy server and the ASGI application/ "kind of a web server" (and the workers), due to the asynchronicity of the request processing? 🤔
Ответитьoh finally I found something that explains the full picture without any gaps
ОтветитьExcelent explanation. Thank you for this great video.
ОтветитьЕн аутстендинг експленейшн
ОтветитьFinally good explanation of this theme
ОтветитьThanks for great explanation! Now it makes much more sense why I have to use gunicorn. History part is also awesome telling not only how, but why too.
ОтветитьWow! I learned it perfectly! that's really really good!
ОтветитьCharacter In the video It's great, I like it a lot $$
ОтветитьExcellent style of presentation. Love the historical contexts/rationales. Thanks!
ОтветитьThank you
ОтветитьThis is terrifyngly useful! Thank you very much for uploading :)
ОтветитьTo the point explanation , Great thanks :)
ОтветитьBest explanation so far
ОтветитьHello, Thank you for the lesson! Exxtremly clear and concise information are presented in this video.
I didn't understand something: if the process is pre-forked, then how can we pass the requests data through environment variables when the request arrives ???
Thanks for clearing my thought on WSGI
ОтветитьGreat explanation, thank you!
ОтветитьBest video that I found that explain how CGI works.
ОтветитьExcellent
ОтветитьThanks! Useful video
Ответитьgreat lesson
ОтветитьExcellent explanation, thanks for sharing. 👍🏼
Ответить