export default {};

var Twitter = require('twit-stream');
var keys =require('./authentication.js');


var stream = new Twitter(keys).stream('statuses/sample');

/// connection configuration for stream object to connect to API

stream.on('connected', function(msg) {
    console.log('Connection successful.');
});

stream.on('reconnect', function(req, res, interval) {
    console.log('Reconnecting in ' + (interval / 1e3) + ' seconds.');
});

stream.on('disconnect', function(msg) {
    console.log('Twitter disconnection message');
    console.log(msg);
});

export default {};

var Twitter = require('twit-stream');
var keys =require('./authentication.js');


var stream = new Twitter(keys).stream('statuses/sample');

/// connection configuration for stream object to connect to API

stream.on('connected', function(msg) {
    console.log('Connection successful.');
});

stream.on('reconnect', function(req, res, interval) {
    console.log('Reconnecting in ' + (interval / 1e3) + ' seconds.');
});

stream.on('disconnect', function(msg) {
    console.log('Twitter disconnection message');
    console.log(msg);
});


// connection returns if twitter cuts off connection and why
stream.on('warning', function(message) {
    console.warning('Yikes! a Warning message:');
    console.warning(message);
});

stream.on('limit', function(message) {
    console.log('WOAH! issued a limit message:');
    console.log(message)
})

stream.on('disconnect', function(message) {
    console.log('NOPE! disconnection message');
    console.log(message);
});

Add event return listeners for Twitter warning,limit and discnct
Add event return listeners for Twitter warning,limit and discnct

considering the amount of information you will be processing it
is more imperative for you to take into account and work on being
able to keep track of what twitters feedback is going to be. Thus
created a series of event listeners for message feedback from
twitter in the case.
