Using Angular JS, what is the correct way to close a web socket connection upon route change?

Question

The question is fairly self explanatory.

If I open a web socket connection in an Angular JS via a controller, it will remain open after navigation (route change).

This is normal behaviour of course, but I was wondering what might be the "best practice" way to request the connection be closed upon navigation.

I could obviously hook in to the $routeChange... methods and broadcast to the controller. But am I missing something? Is there a better way?

If your controller dies because of the route-change you could try listening for a `$destroy` event on the controller's `$scope`? — ivarni, Jul 14 '14 at 09:55
More on that here: https://stackoverflow.com/questions/16094940/what-is-the-lifecycle-of-an-angularjs-controller — ivarni, Jul 14 '14 at 10:07
@ivarni ok thanks. So binding to `$scope.$on("$destroy")` would be the answer. Would you like to answer the question? — LiverpoolsNumber9, Jul 14 '14 at 10:40

score 3 · Accepted Answer · edited May 23 '17 at 12:05

3

Listen for the $destroy event on your controller's $scope and clean up everything that needs cleaning up, in your case that would be closing the websocket connections.

$scope.$on('$destroy', function(event) {
    ...
});

Some more background on the lifecycle of angular controllers can be found in this answer.

edited May 23 '17 at 12:05

Community

1
1

answered Jul 14 '14 at 10:50

ivarni

17,658
17
76
92

Using Angular JS, what is the correct way to close a web socket connection upon route change?

1 Answers1