[Catalyst-commits] r12390 - trunk/examples/CatalystAdvent/root/2009/pen

[t0m at dev.catalyst.perl.org]

Author: t0m
Date: 2009-12-15 22:29:09 +0000 (Tue, 15 Dec 2009)
New Revision: 12390

Modified:
   trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod
Log:
Moar words

Modified: trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod	2009-12-15 21:42:01 UTC (rev 12389)
+++ trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod	2009-12-15 22:29:09 UTC (rev 12390)
@@ -24,10 +24,36 @@
 
 =head2 How?
 
-Well, if your app is small, and as a first implementation, then using the
-L<serve_static_file|Catalyst::Plugin::Static::Simple/serve_static_file> method is a good way to
-start when prototyping your system.
+As a first implementation, then using the
+L<serve_static_file|Catalyst::Plugin::Static::Simple/serve_static_file>
+method is a good way to start.
 
+If your app is small and for internal company use only, then you quite possibly never need
+to go any further...
+
+However, if you're serving large files and likely to have an appreciable number of users,
+then sending bytes in perl just won't scale..
+
+=head2 Scaleing
+
+The key to scaleing is to do things using the minimum resources possible. Sending bytes across
+the internet is something that web servers are very good at scaling to do.
+
+So the planned architecture will be something like:
+
+=item *
+
+Catalyst application running as FastCGI with a limited number of workers
+
+=item *
+
+Light weight web server config with C<X-Accel-Redirect> or C<X-Sendfile> support.
+
+=head3 A note on web servers
+
+Apache is generally thought of as I<big>, but this is very much to do with what
+modules you have loaded and what MPM you're using.
+
 X-Accel-Redirect
 
 X-Sendfile