The first example that comes to mind is Mojo::UserAgent, which uses a secondary IOLoop (from its ioloop attribute) for blocking requests, so that it can run them in a blocking manner even while the main loop is active.
This mailing list is sorta deprecated for the Github discussions forum: https://github.com/mojolicious/mojo/discussions -Dan On Fri, Feb 19, 2021 at 6:01 PM Felipe Gasper <fel...@felipegasper.com> wrote: > Hello, > > In a PR thread yesterday Sebastian mentioned that Mojo allows > multiple concurrent event loops. > > When and why would someone want such a configuration? > > Thank you! > > cheers, > -Felipe Gasper > > -- > You received this message because you are subscribed to the Google Groups > "Mojolicious" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mojolicious+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mojolicious/EED46BD6-1A44-4B7C-B5C9-50A4D276D17B%40felipegasper.com > . > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mojolicious/CABMkAVWBkwcTBb3PYwUHCEoVk717HhGoeD%3D8-rxJabuFB_%3DnFA%40mail.gmail.com.
