On Wednesday, May 4, 2016 at 1:09:50 PM UTC+2, Heiko Jansen wrote: > > Am Montag, 2. Mai 2016 17:20:47 UTC+2 schrieb Matija Papec: >> >> >> I want to read from redis in non-blocking way and delay() looks like >> first choice for this kind of task (event callbacks are closures to session >> related variables). >> > > Using delay() for non-blocking handling of requests (or more specifically > websocket messages) is fine; > the question was why you try to define the event handlers inside some > delay step. > I´d suggest re-reading the relevant docs ( > http://mojolicious.org/perldoc/Mojolicious/Guides/Tutorial#WebSockets > <http://www.google.com/url?q=http%3A%2F%2Fmojolicious.org%2Fperldoc%2FMojolicious%2FGuides%2FTutorial%23WebSockets&sa=D&sntz=1&usg=AFQjCNEtzIPjrRHHXudPG9NkN2Z6wmZH7A> > > and > http://mojolicious.org/perldoc/Mojolicious/Guides/Cookbook#WebSocket-web-service > ). > > Ok, but I didn't notice explicit advice to avoid Delay when establishing ws connection. Furthermore it poses problem only for desktop and mobile Chrome (IE11/Edge/mobile WP/FF were working fine).
And on top of that, everything behaves correct even for Chrome when in such case blocking Redis2 api is used. regards -- 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 https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
