Re: Mojolicious: keeping track of connections with forking

Replies are listed 'Best First'.
Re^2: Mojolicious: keeping track of connections with forking by Rodster001 (Pilgrim) on May 15, 2017 at 19:33 UTC
I keep track of everything in memory with memcache. Like I said, it works great with morbo. But the forking in hypnotoad breaks it.	[reply]
Re^3: Mojolicious: keeping track of connections with forking by Anonymous Monk on May 16, 2017 at 02:49 UTC
I keep track of everything in memory with memcache. Like I said, it works great with morbo. But the forking in hypnotoad breaks it. Try https://metacpan.org/release/Mercury	[reply]
Re^4: Mojolicious: keeping track of connections with forking by Rodster001 (Pilgrim) on May 16, 2017 at 16:21 UTC
Actually, after reading about this closer, it doesn't look like this is possible yet. From this page: http://search.cpan.org/~preaction/Mercury-0.012/lib/Mojolicious/Plugin/Mercury.pm NOTE: Since Mercury does not yet have a way for brokers to share messages, you must run Mercury as a single process. You cannot run Mercury under Hypnotoad like other Mojolicious applications, nor prefork or other multi-processing schemes. See https://github.com/preaction/Mercury/issues/35 to track the clustering feature. So, I guess for now the solution is to run under Morbo until this is resolved either by Mercury or Mojolicious.	[reply]
Re^4: Mojolicious: keeping track of connections with forking by Rodster001 (Pilgrim) on May 16, 2017 at 16:10 UTC
This looks exactly like what I need. Thanks!	[reply]