Smooth restarting for Morbo

[kraih]

This change could eliminate the downtime between Morbo restarts, but it is not yet ready to be merged into master. So far it is completely untested on Windows and the name of the new Mojo::IOLoop method still has to be decided (currently acceptor).

[harvested]

Hi,
I just saw the tweet regarding Morbo and I'm willing to to some windows tests if you need me
Just write me and let me know

Cheers,
Andrei

[kraih]

@harvested Yes please! I just need to know if Morbo restarting still works on Windows.

[harvested]

@kraih Ok, I will, but it will be done later today as it seems I don't have access to GitHub from work :|

[kraih]

We still need Windows test results, but we've decided that we want the feature for Unix either way, and would just disable it on Windows if it doesn't work.

[kraih]

Having everything merged into master should make testing a lot easier though, since you can just download the tarball.

[ghost]

Will look into this later, same with github access here.

On 27.11.2012, at 12:30, Sebastian Riedel notifications@github.com wrote:

Having everything merged into master should make testing a lot easier though, since you can just download the tarball.

—
Reply to this email directly or view it on GitHub.

[tianon]

We set MOJO_LISTEN to a custom value inside our main application script, and are now seeing cases where Morbo (apparently) tries to attach to the default 3000 port (which we use with another application), hence fails with "Can't create listen socket: Address already in use at .../Mojo/IOLoop.pm line 158." As soon as we stop that other application and free up port 3000, Morbo successfully starts with our custom ports from MOJO_LISTEN. Would you like me to open a new ticket for this issue?

[yosifkit]

Adding to the comment above by tianon: it binds to port 3000 (but not listens) even though the MOJO_LISTEN is set to a different port.

[kraih]

This issue is finished, the code has been merged and released to CPAN. If you believe it has introduced new bugs, please open a new issue.