Um pouco da origem para chegar no WSGI

Web Forms

/index.html CLIENT SERVER REQUEST 1989

/index.html CLIENT SERVER REQUEST <html> <h1>Hello!</h1> </html>

CLIENT SERVER RESPONSE Hello!

GET /mypage.html HTTP/1.0 User-Agent: NCSA_Mosaic/2.0 (Windows 3.1) 200 OK Date:
Tue, 15 Nov 1994 08:12:31 GMT Server: CERN/3.0 libwww/2.17 Content-Type: text/html <HTML> A page with an image <IMG SRC="/myimage.gif"> </HTML> https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP Exemplo request/response

Web estática por design

CLIENT SERVER 1991

CLIENT SERVER <form action=”/cgi/form.py” method=”post”> <input name=”full_name”> <input name=”email”> <input
name=”message”> <input type=”submit” value=”Submit”> </form> REQUEST HTTP SERVER RUN SCRIPT + Print output ENV VARs read (STDIN, $query_string, $ENV{'CONTENT_LENGTH'}); Perl Bash Python

CLIENT SERVER REQUEST HTTP SERVER RUN SCRIPT + Print output
HTTP SERVER RESPONSE print(“Contato Enviado!”) Contato Enviado!

- Muitos http servers - Muitas formas de nomear variáveis
para rodar scripts - Scripts não eram portáveis entre diferentes http web servers - Desenvolvedores queriam um padrão para nomear as variáveis e deixar scripts portáveis e padronizados Problemas no início dos forms:

The Dark Side of the Moon CGI Common Gateway Interface
(speciﬁcation) 1993 início 1997 mais popular https://en.wikipedia.org/wiki/Common_Gateway_Interface https://www.jmarshall.com/easy/cgi/portuguese/

https://help.hcltechsw.com/dom_designer/9.0.1/appdev/H_TABLE_OF_CGI_VARIABLES_3561.html

https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP Mas e o WSGI? Browser Web Server Python Web
App HTTP WSGI

Com diversos Python Web frameworks… Precisava padronizar a forma que
os scripts eram chamados e não só as variáveis de ambientes…

Python Web Server Gateway Interface Or WSGI == “wizgy” https://www.python.org/dev/peps/pep-0333/

2003 https://ruslanspivak.com/lsbaws-part2/

Roger Camargo https://huogerac.hashnode.dev

Um pouco da origem para chegar no WSGI

Um pouco da origem para chegar no WSGI

Roger Camargo

More Decks by Roger Camargo

Other Decks in Programming

Featured

Transcript

Web Forms

/index.html CLIENT SERVER REQUEST 1989

/index.html CLIENT SERVER REQUEST <html> <h1>Hello!</h1> </html>

CLIENT SERVER RESPONSE Hello!

GET /mypage.html HTTP/1.0 User-Agent: NCSA_Mosaic/2.0 (Windows 3.1) 200 OK Date:

Web estática por design

CLIENT SERVER 1991

CLIENT SERVER <form action=”/cgi/form.py” method=”post”> <input name=”full_name”> <input name=”email”> <input

CLIENT SERVER REQUEST HTTP SERVER RUN SCRIPT + Print output

- Muitos http servers - Muitas formas de nomear variáveis

The Dark Side of the Moon CGI Common Gateway Interface

https://help.hcltechsw.com/dom_designer/9.0.1/appdev/H_TABLE_OF_CGI_VARIABLES_3561.html

https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP Mas e o WSGI? Browser Web Server Python Web

Com diversos Python Web frameworks… Precisava padronizar a forma que

Python Web Server Gateway Interface Or WSGI == “wizgy” https://www.python.org/dev/peps/pep-0333/

2003 https://ruslanspivak.com/lsbaws-part2/

Roger Camargo https://huogerac.hashnode.dev