AnyEvent::DBI (http://search.cpan.org/~mlehmann/AnyEvent-DBI-2.3/DBI.pm) doesn't appear to be the most popular module in the world -- I can't find many examples at all, so I'm not sure if I'm using it properly.
code => https://gist.github.com/delias-/de01303683a88c3738c4 >From my understanding, the way I've written this will do the following on every page load when $self->sel is called: 1. fork a child 2. open a new connection to an oracle DB (kind of concerned about this actually -- A submodule named AnyEvent::DBI::MySQL is smart enough to use connect_cache and reclaim disconnected db handles for later reuse during the 'destroy' action) 3. prepare/execute a query on every page load. 4. dbh will go out of scope and be destroyed. Do I even need to bother with the brodcast/wait/send/recv stuff at all? Eventually I'm just going to put a button on the page that makes an AJAX call to $self->sel('100') and updates the page when it returns. Since this module forks a thread it shouldn't bog down the actual router or controller to affect multiple users hitting the page, is that correct? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
