COME SALVARSI DALLE RELATIVE ✍🏻
#scrittura#writingtips
Le relative, già. Una trappola per chi scrive. Se ne usiamo troppe diamo prova di una scrittura ingenua e poco curata.
"Arrivò quell'uomo che era già stato visto nel locale e che di certo cercava qualcuno".
Ma come facciamo a evitarle, sembrano così necessarie? Ecco due suggerimenti.
1️⃣Costruirefrasi più brevi✍🏻
Scrivere frasi più brevi invece di evoluzioni sintattiche aggrovigliate su se stesse (Si poteva scrivere: che si aggrovigliano, ma come vedete ci sono altre soluzioni).
2️⃣Usare i due punti ✍🏻
Utilizzate i salvifici due punti, aiutano sempre a risolvere le situazioni in cui abbondano le relative.
Ecco dunque che possiamo scrivere:
"Arrivò quell'uomo: era già stato visto nel locale, di certo cercava qualcuno".
❇️ Rendi fluida la scrittura.
@writingway
🙌Se ti è piaciuto questo post e pensi possa interessare ad altri, inoltralo cliccando sulla freccia a destra.
https://docs.djangoproject.com/en/1.11/howto/deployment/wsgi/
How to deploy with #WSGI
Django’s primary deployment platform is WSGI, the Python standard for web servers and applications.
Django’s startproject management command sets up a simple default WSGI configuration for you, which you can tweak as needed for your project, and direct any WSGI-compliant application #server to use.
#django
https://github.com/Miserlou/Zappa#about
Zappa makes it super easy to build and deploy all Python #WSGI applications on #AWS Lambda + #API Gateway. Think of it as "#serverless" #web hosting for your Python apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments!
If you've got a Python web app (including Django and Flask apps), it's as easy as:
$ pip install zappa
$ zappa init
$ zappa deploy
and now you're server-less! Wow!
What do you mean "serverless"?
Okay, so there still is a server - but it only has a 40 millisecond life cycle! Serverless in this case means "without any permanent infrastructure."
http://www.jaggedverge.com/2017/11/how-a-web-page-request-makes-it-down-to-the-metal/
How a web page request makes it down to the metal
by : Janis Posted in : Tutorials, work-in-progess Tags : #NGINX, #Python No Comments
The other day I was interested in how many steps occur between sending a #POST or #GET#request from a website to the actual processing that happens on the CPU of the #server. I figured that I knew bits and pieces of the puzzle but I wanted to see the complete path from the highest levels of abstraction all the way to the lowest without missing anything too big in-between. It turns out that in a modern web system there are a lot of steps. I have been really fascinated by this much like the explorer that wants to find a path from one known place to another. If you are interested in better understanding how your computer works you might find walking along this path with your tech stack helpful.
Frontend
prelude: GET request
Browser page #rendering
POST request
sidenote: #CSRF#token
Network stack
sidenote: The Internet
#TCP
sidenote: more comprehensive treatment of network stack
Backend
Handling web request
#WSGI
#Django
Django URL routing
Django views
Python implementations
#CPython
CPython bytecode
CPython bytecode execution details
Machine Code
CPython to machine code
Machine code execution
Hardware implementation details
Microcode
Processor #pipeline
Silicon implementation of addition
Silicon adder unit
AND gate
Transistor