Modern Web Development with Perl
•Descargar como ODP, PDF•
11 recomendaciones•32,289 vistas
An introduction to PSGI and Plack that I gave at the London Perl Workshop in December 2010.
![Modern Perl Web Developement Dave Cross Magnum Solutions Ltd [email_address]](https://image.slidesharecdn.com/plack-101205235956-phpapp02/85/Modern-Web-Development-with-Perl-1-320.jpg)
![Web Development ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (16)
Similar a Modern Web Development with Perl
Similar a Modern Web Development with Perl (20)
Más de Dave Cross
Más de Dave Cross (20)
Último
Último (20)
Modern Web Development with Perl
- 1. Modern Perl Web Developement Dave Cross Magnum Solutions Ltd [email_address]
- 3. Surely it is easy now
- 4. Lessons have been learned
- 5. Best practices have been worked out
- 7. Defined the interaction between a web server and a program
- 10. Program processes parameters and produces response
- 11. Response includes program's output
- 13. Form to email
- 14. Guestbook
- 15. Hit counter
- 16. Etc...
- 17. Most of them were written in Perl
- 19. Perl compiler starts up on every request
- 20. Can be very slow
- 21. Not useful for heavy traffic sites
- 23. Apache allowed loadable modules
- 24. mod_perl loads a Perl compiler
- 26. No more start-up costs
- 30. Many programs needed rewrites
- 31. Different input and output methods
- 33. Microsoft IIS
- 34. lighttpd
- 35. Etc...
- 39. Read user input
- 40. Process data
- 41. Produce output
- 42. Let's look at input and output in more detail
- 48. Handles CGI processing for you
- 49. Input and output
- 50. Output in the form of CGI & HTML helper functions
- 53. What if you have a designer?
- 54. HTML experts don't always know Perl
- 55. Use a templating system instead
- 59. Use tags where the variable output goes
- 60. Easier to edit by your HTML team
- 63. Parameters encoded in the URL
- 65. Need to access these parameters
- 66. N.B. I'm deliberately ignoring POST requests for simplicity
- 70. Apache2::Request
- 71. Other environments have different methods
- 72. This is where PSGI comes in
- 73. PSGI & Plack
- 76. Plack is a reference implementation (based on Ruby's Rack)
- 78. There are many ways to write web applications in Perl
- 79. Each is subtly different
- 80. Hard to move an application between server architectures
- 82. FastCGI
- 83. mod_perl
- 84. etc...
- 86. Each creates applications in subtly different ways
- 87. Hard to port applications between them
- 89. PSGI is that specification
- 92. Passed a reference to an environment hash
- 94. Headers
- 95. Body
- 106. Drop in into a configured PSGI-aware web server
- 107. Browse to URL
- 109. $ plackup app.psgi HTTP::Server::PSGI: Accepting connections at http://localhost:5000/
- 119. Parse the query string from the $env hash
- 120. Ask the Plack::Request object
- 125. This is left as an exercise for the reader
- 127. The secret is in the 'path_info' input
- 128. $env->{PATH_INFO}
- 129. /
- 130. /person/1
- 131. /person/1/delete
- 134. Catalyst
- 135. Dancer
- 136. Mojolicious
- 137. etc...
- 138. Advanced Plack
- 140. Returns another PSGI application
- 141. Simple spec makes this easy
- 142. Plack::Middleware::*
- 143. Plack::Builder adds middleware configuration language
- 154. Catalyst, CGI::Application, Dancer, Jifty, Mason, Maypole, Mojolicious, Squatting, Web::Simple
- 155. Many more
- 157. use MyApp; MyApp->setup_engine('PSGI'); my $app = sub { MyApp->run(@_) };
- 161. Starman, Starlet, Twiggy, Corona, HTTP::Server::Simple::PSGI
- 164. mod_psgi
- 168. Plack is an implementation
- 169. PSGI makes your life easier
- 170. Most of the frameworks and server you use already support PSGI
- 171. No excuse not to use it
- 173. perldoc Plack