Mojo::Reactor

[Stefan Adams]

There's a current PR for addressing an issue regarding Mojo::Reactor. I feel like I have a good understanding of all the parts of Mojolicious, except Mojo::Reactor. I simply do not understand it at all. My confusion is increased by the similarity with Mojo::IOLoop. Much of the docs make use of IOLoop modules but I can't think of an example that uses Reactor.

Can anyone provide some insight into this module, what it's for, and how and why it's different from IOLoop?

[Dan Book]

The reactor is essentially an abstract class for low level event loop implementations, stripped to the functionality that each implementation can implement differently. They don't do anything except watch filehandles and set timers, start and stop, and run callbacks when something happens while running. Mojo::IOLoop is the user interface that can decide what reactor implementation to use, implements the singleton that different parts of the process can hook into, and implements higher level abstractions like streams, clients, and servers.

-Dan

On Sat, Apr 18, 2020 at 11:26 PM Stefan Adams <s103...@gmail.com> wrote:

There's a current PR for addressing an issue regarding Mojo::Reactor. I feel like I have a good understanding of all the parts of Mojolicious, except Mojo::Reactor. I simply do not understand it at all. My confusion is increased by the similarity with Mojo::IOLoop. Much of the docs make use of IOLoop modules but I can't think of an example that uses Reactor.

Can anyone provide some insight into this module, what it's for, and how and why it's different from IOLoop?

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojolicious/CACyQ%2BFQPo67qOjjr7xuWSeTb%2BC8axQUVEqiHWg3_ryBE6Q8TQg%40mail.gmail.com.