Date: 2009-03-11 02:28:50 +0000 (Wed, 11 Mar 2009)
Fix a doc typo reported by Abhijit Menon-Sen.
--- trunk/poe/lib/POE/Kernel.pm 2009-03-11 02:14:13 UTC (rev 2500)
+++ trunk/poe/lib/POE/Kernel.pm 2009-03-11 02:28:50 UTC (rev 2501)
@@ -2847,10 +2847,12 @@
being used. Since most graphical toolkits include some form of event
loop, back-end code should be portable to all of them.
-Cooperation with other event loops also lets you embed POE code into
-other software. For example, one can embed networking code into Vim,
-so non-blocking HTTP clients into irssi because they all cooperatively
+POE's cooperation with other event loops lets POE be embedded into
+other software. The common underlying event loop drives both the
+application and POE. For example, by using POE::Loop::Glib, one can
+embed POE into Vim, irssi, and so on. Application scripts can then
+take advantage of POE::Component::Client::HTTP (and everything else)
+to do large-scale work without blocking the rest of the program.
Because this is Perl, there are multiple ways to load an alternate
event loop. The simplest way is to load the event loop before loading
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.