The web in a box - a next generation web framework for the Perl programming language

IRC log for #mojo, 2016-07-23

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:10 sri mishanti1: and speaking of minion, a little logo might be cool too
01:10 dvinciguerra_ joined #mojo
02:17 ningu joined #mojo
02:44 kid51 joined #mojo
02:44 noganex joined #mojo
03:06 asarch joined #mojo
03:31 sri this is a great explanation for why we can never have exact rules for what's acceptable behavior in a community https://eev.ee/blog/2016/07/22/on-a-technicality/
04:29 kaare joined #mojo
04:59 jberger mishanti1: that's really cool thanks! I hope we fine a good way to make use of it a
05:13 disputin joined #mojo
05:33 PopeFelix joined #mojo
05:39 punter joined #mojo
05:40 jberger sri: That is a really good article
06:21 meshl joined #mojo
06:27 dod joined #mojo
06:30 absolut_todd joined #mojo
06:32 dod joined #mojo
06:51 che-quest joined #mojo
07:08 eseyman joined #mojo
07:40 dod joined #mojo
07:54 Vandal joined #mojo
08:56 cpan_mojo Mojolicious-Plugin-HostMeta-0.21 by AKRON https://metacpan.org/release/AKRON/Mojolicious-Plugin-HostMeta-0.21
09:05 Craftsmanship joined #mojo
09:11 Craftsmanship I'd like to hook my UserAgents so i can log stuff, but I don't see a way to add an on_success callback that's not the regular one used where the requests are enqueued
09:24 batman Craftsmanship: $ua->on(start => sub { my ($ua, $tx) = @_; $tx->on(finish => sub { warn "done" }); warn "started"; });
09:24 batman maybe something like that? ^^
09:26 jamesaxl joined #mojo
09:26 rwar joined #mojo
09:28 Craftsmanship oh, 'cause I want the end of the transaction, not the UA...
09:28 Craftsmanship makes sense.
09:32 batman :)
09:32 jberger Craftsmanship: why not just use that callback though? Unless these are synchronous requests?
09:34 Craftsmanship 'cause it's for logging and i want it to happen whenever the UA is used, and i'm bad at remembering to copy/pasta book keeping code into places until after I need it
09:35 jberger Ah point
09:35 jberger Then yeah, what batman said
09:44 dod joined #mojo
09:48 Craftsmanship Are there safe places in $tx that I can shove things, or should i just pick something nobody will ever want to use in future releases?
09:48 Craftsmanship (i mean, i could inside-out it, i guess)
09:53 jberger Just close over some variable
09:57 Craftsmanship The value is from the future :S
10:06 jberger Sure?
10:07 jberger The container is all you need
10:14 Craftsmanship Fine, I'll admit it, i'm logging my http transactions over http
10:15 Craftsmanship (I haven't figured out how to log the results of the logging POSTs yet, but one meta-problem at a time)
10:27 batman Craftsmanship: it's the same $tx in both the start and finish event, so i'm not sure what you need to store outside of those callbacks.
10:28 batman you have $tx->req and $tx->res in both events
10:51 cuechan joined #mojo
10:52 Vandal joined #mojo
10:56 bobkare joined #mojo
11:04 Craftsmanship Well, mostly that stuff in $tx will change and my thing will break - i guess it's going to remain hash-ref backed and as long as I don't pick a key that's in use it'll me fine
11:05 kid51 joined #mojo
11:16 cuechan_ joined #mojo
11:20 cuechan_ joined #mojo
11:21 ningu joined #mojo
11:27 batman wonder what "stuff in $tx" means...
11:41 Craftsmanship joined #mojo
11:43 Craftsmanship I'm just asking what the contract is for "things I stuff in the keys of Mojo::UserAgent::Transactor"
11:56 pink_mist the contract is: don't
11:56 pink_mist unless it's a documented feature
12:16 dod joined #mojo
12:44 zivester joined #mojo
12:46 Craftsmanship Sounds fair.
12:56 punter joined #mojo
13:22 kaare joined #mojo
13:40 kaare joined #mojo
13:50 Vandal joined #mojo
13:53 Vitrifur joined #mojo
14:15 tencendur joined #mojo
14:31 kaare joined #mojo
15:00 batman i abuse" $tx->req->env ... it's not very nice, but sometimes i do :P
15:05 Adura joined #mojo
15:10 sri :o
15:11 kaare joined #mojo
15:21 kaare_ joined #mojo
15:22 ningu joined #mojo
15:54 Vandal joined #mojo
16:51 kaare joined #mojo
16:56 kid51 joined #mojo
17:00 dod joined #mojo
17:35 PryMar56 joined #mojo
18:02 cosimo joined #mojo
18:15 kid51 joined #mojo
18:20 jberger I still don't understand what you need to do that you couldn't with a hash ref that you close over
18:28 ningu joined #mojo
18:39 trone joined #mojo
18:45 pkuptsov joined #mojo
18:56 sri \o\
18:56 sri /o/
18:59 dod joined #mojo
19:05 jberger http://www.prh.noaa.gov/cphc/tc_graphics/2016/graphics/EP052016W.gif
19:05 jberger :s
19:06 punter joined #mojo
19:11 punter joined #mojo
19:12 punter joined #mojo
19:22 kaare_ joined #mojo
19:46 kaare_ joined #mojo
20:14 ningu joined #mojo
21:10 punter joined #mojo
21:17 dvinciguerra_ joined #mojo
22:42 lluad joined #mojo
23:20 sri jberger: how complete is Minion::Monitor anyway?
23:25 sri i mean, there can't be that much missing
23:26 sri and not having to care about design, finishing it can't be that much work either?
23:28 cuechan joined #mojo
23:28 sri this is basically what i was hoping for with a minion ui http://cdn.hangfire.io/img/ui/dashboard.png
23:29 sri just a dashboard with stats, job listing, worker listing, form to add jobs
23:30 sri job listing with filter by state (like error), detail view to review results/errors, and buttons for retry/remove
23:31 sri that's about it
23:31 * sri would be happy to merge that into minion
23:31 sri oh, and clean code of course, this will likely be reviewed as an example by users
23:33 mishanti1 Making it clean and easy to get that "at a glance overview" is important.
23:33 sri yea
23:33 mishanti1 And just as important: make it feel natural on mobile devices.
23:34 mishanti1 Few things are more annoying that _not_ being able to use a UI effectively on smaller devices.
23:34 dvinciguerra_ joined #mojo
23:36 ningu joined #mojo
23:37 sri without making it mobile specific
23:38 sri can't tell you how much i hate it when i get a completely different site on mobile
23:38 ningu if I have nginx running in front of a hypnotoad-deployed mojolicious app, and nginx has http/2 enabled, does that mean I take full advantage of http/2 for the mojolicious app? I'd assume so, since the backend just has a reverse proxy and that probably doesn't make a difference whether it's http 1.0/1.1/2?
23:39 sri mostly yes
23:39 sri i imagine nginx doesn't support http/2 server push
23:39 ningu what are the situations where native http/2 support would matter for hypnotoad?
23:40 ningu ah, not sure
23:40 mishanti1 sri: The general layout need to be different, to a point, but the "flow" and feel of the application need to be the same. If the experience is drasticly different on desktop and mobile you've usually missed the mark.
23:41 mishanti1 That said: there are some situations in which making them distinctly different is the right thing to do, but those cases are few and far between.
23:47 cuechan joined #mojo

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary