3.0.2 • Published 12 years ago
scalable-server v3.0.2
Scalable Server
Initiation
var Server = require('scalable-server');
var config = {
daemon: {
port: 8800,
clients: [],
servers: [],
noEvents: false
},
test: false
};
var s = new Server(config);
// connect listeners
s.on('connection.new', function(event) { /* .. code .. */ });
s.on('connection.lost', function(event) { /* .. code .. */ });
s.init();
// connect to additional clients and servers
// this can also be done from the config
s.getDaemon().addClient( port );
s.getDaemon().addServer( address ); // example : ws://localhost:9000/Options
The options are given to the constructor
Daemon Options
This is in the daemon property of the config object.
portSets the server port on the entered number, the default is8800clientsAdds a connection to a client, this parameter can be repeated when required. This only requires a port numberserversAdds a connection to a server, this parameter can be repeated when required. This requires an object with the following attributeshostnameThe hostname to connect toportThe port to connect to
noEventsIftrue, this sets the event handling tomessageevents only. This effectively disables the use ofevt.*events.
clientsis the shorthand version ofserverswhere the hostname is always "localhost"
Events
Global
logThis event is emitted every time a log line is executed, this can be used to handle logs in your own way, instead of outputting them to the consolemessageThis event is emitted every time a message is received, this is only triggered once per message. The handler for this parameter has 2 parameters;messageThe message object, this includes the message, user, hashcode and event-type.connectionThe connection which has send this message.
evt.<eventcode>This type of event is send whenever the client or a connected server sends out a message with the event type set. Note: this will be triggered instead of themessageevent. This can be configured.Example:
Client:
{ "user": "hank", "event":"request", "method":"sayHello", "params": {} }Server:
self.emit('evt.request', event);
If you put the returnValue of the EventObject to false, the message will not be send to other servers, nor clients. This allows to respond to an event without alerting the flock.
Connection
connection.newThis event is emitted when a new connection is established. The handler for this event has one parameter, which is the connection object itself.connection.lostThis event is emitted when a connection is lost. The handler for this event has one parameter, which is the connection object itself. Note: one can no longer use this object for sending messages. The connection has been terminated.
Server
server.newThis event is emitted when a new server-connection is established. The handler for this event has one parameter, which is the connection object itself.server.lostThis event is emitted when a server-connection is lost. The handler for this event has one parameter, which is the connection object itself. Note: one can no longer use this object for sending messages. The connection has been terminated.
Sub Modules
TBD
Objects
Submodule
Submodule: {
server: null, // Deamon
// ...
init:function(){} // Function
}Connection
Connection: {
pool: [], // ConnectionPool[]
conn: null, // Websocket
// ...
getIndex: function() {}, // int
remove: function() {}, // void
send: function(message) {} // void
}Connection Pool
ConnectionPool: {
pool:[], // Connection[]
// ...
getPool: function() {}, // Connection[]
setPool: function(connections) {}, // void
add: function(connection) {}, // Connection
remove: function(index) {}, // Connection
has: function(index) {} // boolean
index: function(connection) {}, // int
send: function(message, except_connection) {} // void
]EventObject
EventObject: {
event: "", // String
returnValue: true, // boolean
// ...
message: "", // String
connection: null // Connection
}