Bower Component for using AngularJS with Socket.IO, based on this.
bower install angular-socket-ioor download the zip.- Make sure the Socket.IO client lib is loaded. It's often served at
/socket.io/socket.io.js. - Include the
socket.jsscript provided by this component into your app. - Add
btford.socket-ioas a module dependency to your app.
This module exposes a socketFactory, which is an API for instantiating
sockets that are integrated with Angular's digest cycle.
// in the top-level module of the app
angular.module('myApp', [
'btford.socket-io',
'myApp.MyCtrl'
]).
factory('mySocket', function (socketFactory) {
return socketFactory();
});With that, you can inject your mySocket service into controllers and
other serivices within your application!
Building on the example above:
// in the top-level module of the app
angular.module('myApp', [
'btford.socket-io',
'myApp.MyCtrl'
]).
factory('mySocket', function (socketFactory) {
return socketFactory();
}).
controller('MyCtrl', function (mySocket) {
// ...
});For the most part, this component works exactly like you would expect.
The only API addition is socket.forward, which makes it easier to add/remove listeners in a way that works with AngularJS's scope.
Takes an event name and callback. Works just like the method of the same name from Socket.IO.
Takes an event name and callback. Works just like the method of the same name from Socket.IO.
Takes an event name. Works just like the method of the same name from Socket.IO.
Sends a message to the server. Optionally takes a callback.
Works just like the method of the same name from Socket.IO.
socket.forward allows you to forward the events received by Socket.IO's socket to AngularJS's event system.
You can then listen to the event with $scope.$on.
By default, socket-forwarded events are namespaced with socket:.
The first argument is a string or array of strings listing the event names to be forwarded.
The second argument is optional, and is the scope on which the events are to be broadcast.
If an argument is not provided, it defaults to $rootScope.
As a reminder, broadcasted events are propagated down to descendant scopes.
An easy way to make socket error events available across your app:
// in the top-level module of the app
angular.module('myApp', [
'btford.socket-io',
'myApp.MyCtrl'
]).
factory('mySocket', function (socketFactory) {
var mySocket = socketFactory();
mySocket.forward('error');
return mySocket;
});
// in one of your controllers
angular.module('myApp.MyCtrl', []).
controller('MyCtrl', function ($scope) {
$scope.$on('socket:error', function (ev, data) {
});
});Avoid duplicating event handlers when a user navigates back and forth between routes:
angular.module('myMod', ['btford.socket-io']).
controller('MyCtrl', function ($scope, socket) {
socket.forward('someEvent', $scope);
$scope.$on('socket:someEvent', function (ev, data) {
$scope.theData = data;
});
});This option allows you to provide the socket service with a Socket.IO socket object to be used internally.
This is useful if you want to connect on a different path, or need to hold a reference to the Socket.IO socket object for use elsewhere.
angular.module('myApp', [
'btford.socket-io'
]).
factory('mySocket', function (socketFactory) {
var myIoSocket = io.connect('/some/path');
mySocket = socketFactory({
ioSocket: myIoSocket
});
return mySocket;
});This option allows you to set the scope on which $broadcast is forwarded to when using the forward method.
It defaults to $rootScope.
The default prefix is socket:.
To remove the prefix:
angular.module('myApp', [
'btford.socket-io'
]).
config(function (socketFactoryProvider) {
socketFactoryProvider.prefix('');
});angular-socket-io version 0.3 changes X to make fewer assumptions
about the lifecycle of the socket. Previously, the assumption was that your
application has a single socket created at config time. While this holds
for most apps I've seen, there's no reason you shouldn't be able to
lazily create sockets, or have multiple connections.
In 0.2, angular-socket-io exposed a socket service. In 0.3, it
instead exposes a socketFactory service which returns socket instances.
Thus, getting the old API is as simple as making your own socket service
with socketFactory. The examples below demonstrate how to do this.
In most cases, adding the following to your app should suffice:
// ...
factory('socket', function (socketFactory) {
return socketFactory();
});
// ...Before:
angular.module('myApp', [
'btford.socket-io'
]).
config(function (socketFactoryProvider) {
socketFactoryProvider.prefix('foo~');
socketFactoryProvider.ioSocket(io.connect('/some/path'));
}).
controller('MyCtrl', function (socket) {
socket.on('foo~bar', function () {
$scope.bar = true;
});
});After:
angular.module('myApp', [
'btford.socket-io'
]).
factory('socket', function (socketFactory) {
return socketFactory({
prefix: 'foo~',
ioSocket: io.connect('/some/path')
});
}).
controller('MyCtrl', function (socket) {
socket.on('foo~bar', function () {
$scope.bar = true;
});
});Closed issues labelled FAQ might have the answer to your question.
MIT
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent