Create an account at http://www.pubnub.com/account
http://www.pubnub.com - PubNub Real-time Push Service in the Cloud.
The PubNub Network is a blazingly fast Global Messaging Service for building real-time web and mobile apps. Thousands of apps and developers rely on PubNub for delivering human-perceptive real-time experiences that scale to millions of users worldwide. PubNub delivers the infrastructure needed to build amazing Mobile, MMO games, social apps, business collaborative solutions, and more.
You may access the latest PubNub JavaScript SDK on The PubNub Network CDN.
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo'
});
})();</script>NOTE: SSL Mode requires a few extra steps: SSL MODE
It is important to note that you must never use JSON.stringify()
when sending signals/messages via PUBNUB.
Why? Because the serialization is done for you automatically.
Instead just pass the full object as the message payload.
PubNub takes care of everything for you.
pubnub.publish({
channel : "hello_world",
message : { "data" : "Hi." }
})
// -- also
var a = [ 1, 2, { b : 3} ];
pubnub.publish({ channel : "hello_world", message : a })WARNING: Do not use
JSON.stringify().
In the case where the client will never publish and for security considerations, use this following method for initialization:
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
var pubnub = PUBNUB.init({ subscribe_key : 'demo' });
})();</script>NOTE: Copy and paste this example into a blank HTML file or visit http://jsfiddle.net/geremy/SqamR/ to demo
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
// Init
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo'
})
// LISTEN
pubnub.subscribe({
channel : "hello_world",
message : function(m){ alert(m) },
connect : publish
})
// SEND
function publish() {
pubnub.publish({
channel : "hello_world",
message : "Hi."
})
}
})();</script>https://github.com/pubnub/javascript#simple-example - See the simple working example. However if you want to learn the basic code to send/receive, see below :
If you setup credentials using the PUBNUB.init() method, for example:
var p = PUBNUB.init({publish_key : 'demo' , subscribe_key : 'demo'});you access PubNub methods via p's instance methods:
p.publish({
channel : "hello_world",
message : "Hi."
})When working with any non-web JavaScript-based client (such as a mobile JS-based client, like PhoneGap, Titanium, etc), you MUST use this slightly-modified method of instantiation:
var m = PUBNUB({publish_key : 'demo' , subscribe_key : 'demo'});
// no explicit PUBNUB.init() method call!and access PubNub methods via m's instance methods:
m.publish({
channel : "hello_world",
message : "Hi."
})PUBNUB.publish({
channel : "hello_world",
message : "Hi."
})PUBNUB.subscribe({
channel : "hello_world",
message : function(m){ alert(m) }
})NOTE: Start with the WEB directory as the default deployment choice to target all browsers and mobile platforms.
| Directory | Description of the Build |
|---|---|
| examples | Several Sample Web Apps. |
| web | All Mobile and Desktop Browsers 100% supported. |
| modern | Light-weight Build for only the LATEST Browsers. |
| mobile | Light-weight Build for only the LATEST Mobile Apps. |
| titanium | Appcelerator Titanium Build with example project code. |
| node.js | Node.JS SDK (CommonJS). sudo npm install pubnub |
| socket.io | Socket.IO Framework support with examples and videos. |
| phonegap | PhoneGap Build. |
| smart-tv | Sony, Philips, Samsung, LG, Vizio. |
| core | Master Source Files are located here. |
It is a good idea to start with the web directory and work your way further into the platform you are seeking if needed. The web directory supports all legacy, modern and mobile web browsers.
Let's start off with a simple example of how to use the PubNub Network
JavaScript SDK using the web build. It's as easy as copy/paste.
<div id=pubnub pub-key=demo sub-key=demo></div>
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
PUBNUB.subscribe({
channel : "hello_world", // CONNECT TO THIS CHANNEL.
restore : true, // FETCH MISSED MESSAGES ON PAGE CHANGES.
message : function( message, env, channel ) {}, // RECEIVED A MESSAGE.
presence : function( message, env, channel ) {}, // OTHER USERS JOIN/LEFT CHANNEL.
connect : function() {}, // CONNECTION ESTABLISHED.
disconnect : function() {}, // LOST CONNECTION (OFFLINE).
reconnect : function() {} // CONNECTION BACK ONLINE!
})
})();
</script>Sometimes, for several reasons, the publish method will
relay an unsuccessful relay.
You can detect this in order to begin considering a re-publish
decisions in your code.
PUBNUB.publish({
channel : "hello_world",
message : "Hi.",
callback : function(details) {
var success = details[0]
, response = details[1];
if (success) console.log( "Success!", response );
if (!success) console.log( "Fail!", response );
}
})Note: We are using the
callbackparamater and passing a function as the value with a single paramdetails.
Sometimes an error will occur and you may wish to log it. Note that the PubNub JavaScript SDK auto-recovers connections upon error so it is not necessary to act upon errors when receiving messages.
<div id=pubnub pub-key=demo sub-key=demo></div>
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
PUBNUB.subscribe({
channel : "hello_world", // CONNECT TO THIS CHANNEL.
message : function( message, env, channel ) {}, // RECEIVED A MESSAGE.
error : function(data) { console.log(data) } // CONNECTION BACK ONLINE!
})
})();
</script>Note: the
errorcallback is being used.
Multiplexing enhances mobile performance and battery savings.
The PubNub Network today is the only vendor that supports real channel
multiplexing with a single TCP Socket.
With Multiplexing, you are able to subscribe to a group of channels
while conserving device resources and
improving performance of message delivery;
all with a single network connection.
It is easy to use multiplexing with any 3.4 client SDKs because
it is transparent and automatic!
Here is an example of using Channel Multiplexing in JavaScript:
You can continue to add channels with subsequent calls.
NOTE: See the Multiplexing Example: Multiplexing Test
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// Setup your Receiver Function
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
function receiver( message, envelope, channel ) { /*...*/ }
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// ADD ARRAY - You can add an array of channel names to connect.
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.subscribe({
channel : ['chan1','chan2','chan3'],
message : receiver
})
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// ADD LIST - You can add a comma separated list of channel names.
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.subscribe({
channel : 'chan4,chan6,chan7',
message : receiver
})
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// ADD ONE MORE - You can add one channel at a time.
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.subscribe({
channel : 'chan8',
message : receiver
})// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// REMOVE ARRAY
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.unsubscribe({ channel : ['chan1','chan2','chan3'] })
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// REMOVE LIST
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.unsubscribe({ channel : 'chan4,chan6,chan7' })
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
// REMOVE ONE
// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
pubnub.unsubscribe({ channel : 'chan8' })That's it! It's easy to take advantage of multiplexing. If you have any questions please contact help@pubnub.com
It is important to note that you may publish to any channel at any time regardless of being subscribed to that channel.
There is no need to be subscribed to a channel in order to publish.
NOTE: This cryptography is compatible with all other 3.4 PubNub SDKs! Easily encrypt your PubNub messages using AES by setting a single flag when you publish a message and subscribing as well. Even better, this encryption works across all
3.4PubNub clients, meaning you can encrypt/decrypt across these environments.
You can now use PubNub AES256 Cryptograhpy with JavaScript and other SDK languages easily by following this starting point for JavaScript. We’ve worked hard to make sure that using AES encryption in PubNub is easy. The complexity of encrypting and decrypting the data is built into the free PubNub client libraries (since our libraries are open source, you’re welcome to see how we did it). To use AES encryption in PubNub, simply do the following:
<script src=https://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js></script>
<script src=https://pubnub.a.ssl.fastly.net/pubnub-crypto-3.5.47.min.js></script>
<script>(function(){
var secure_pubnub = PUBNUB.secure({
publish_key : 'demo',
subscribe_key : 'demo',
ssl : true,
cipher_key : 'my-super-secret-password-key'
});
secure_pubnub.subscribe({
channel : 'my_channel',
connect : send_hello,
message : receive_hello
});
function receive_hello(hello) {
alert(hello);
}
function send_hello() {
secure_pubnub.publish({
channel : 'my_channel',
message : 'hello!'
});
}
function get_encrypted_history() {
secure_pubnub.history({
channel: channel,
limit: 15,
callback: function(notifications) {
console.log(notifications);
}
});
}
})();</script>http://jsfiddle.net/geremy/8e6Cr/
<span onclick="hereNow()">Click Me for Here Now!</span>
<span onclick="history()">Click Me for History!</span>
<script>(function(){
function hereNow() {
PUBNUB.here_now({
channel : 'hello_world',
callback : function (message) { console.log(message) }
});
}
function history() {
PUBNUB.history({
count : 10,
channel : 'hello_world',
callback : function (message) { console.log(message) }
});
}
})();</script><div id=pubnub ssl=on></div>
<script src=https://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js></script>
<script>(function(){
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo',
origin : 'pubsub.pubnub.com',
ssl : true
});
pubnub.subscribe({
channel : 'my_channel',
connect : function() { /* ... */ },
callback : function(message) {
alert(JSON.stringify(message));
}
});
})();</script>/v2/history/sub-key/<sub-key>/channel/<channel>?URL_PARAMETERS
start (time token): Beginning of a timeline slice (exclusive)
end (time token): Ending of a timeline slice (inclusive)
count (integer): The number of messages to return (default:100, max:100)
callback (string): JSONp callback function
reverse (true/false): If we should traverse the timeline in reverse (default is false).
true: OLDEST --> newest.
false: NEWEST --> oldest.
Returns a JSON Array with three or more elements as follows:
- the list of messages
- the starting slice time token, and
- the ending slice time token.
[[msg, msg, msg], timetoken, timetoken]
Using a combination of start/end/reverse you can:
- Traverse newest to oldest messages (default)
- Traverse oldest to newest (setting reverse=true)
- Page through results by providing a start OR end time token.
- Retrieve a "slice" of the timeline by providing both a start AND end time token.
// ----------------------------------
// Usage Example of get_all_history()
// ----------------------------------
get_all_history({
channel : channel.value,
callback : function(messages) {
console.log(messages)
}
});
// ----------------------------------
// Get All History Example
// ----------------------------------
function get_all_history(args) {
var channel = args['channel']
, callback = args['callback']
, start = 0
, count = 100
, history = []
, params = {
channel : channel,
count : count,
callback : function(messages) {
var msgs = messages[0];
start = messages[1];
params.start = start;
PUBNUB.each( msgs.reverse(), function(m) {history.push(m)} );
if (msgs.length < count) return callback(history);
count = 100;
add_messages();
}
};
add_messages();
function add_messages() { PUBNUB.history(params) }
}http://pubsub.pubnub.com/v2/history/sub-key/demo/channel/storage_test
>>> [["Pub1","Pub2","Pub3","Pub4","Pub5"],13406746729185766,13406746845892666]
http://pubsub.pubnub.com/v2/history/sub-key/demo/channel/storage_test?count=3&reverse=true
>>> [["Pub1","Pub2","Pub3"],13406746729185766,13406746780720711]
http://pubsub.pubnub.com/v2/history/sub-key/demo/channel/storage_test?reverse=true&start=13406746780720711
>>> [["Pub4","Pub5"],13406746814579888,13406746845892666]
http://pubsub.pubnub.com/v2/history/sub-key/demo/channel/storage_test?end=13406746780720711
>>> [["Pub3","Pub4","Pub5"],13406746780720711,13406746845892666]
- start (time token of Tues 26th): 13406688000000000
- end (time token of Wed 27th): 13407552000000000
http://pubsub.pubnub.com/v2/history/sub-key/demo/channel/storage_test?start=13406688000000000&end=13407552000000000
>>> [["Pub1","Pub2","Pub3","Pub4","Pub5"],13406746729185766,13406746845892666]
<div id=pubnub></div>
<script src=http://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js></script>
<script>(function(){
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo'
});
pubnub.history({
count : 10,
channel : 'hello_world',
callback : function (message) { console.log(message) }
});
})();</script>Replay is an API that allows you to "replay" the events of a channel as they happened before in the past. Replay will repeat the message delivery sequence in sync with the timeline as they occured.
NOTE: You must have Storage/Playback enabled on your Account.
<div id=pubnub></div>
<script src=http://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js></script>
<script>(function(){
/* GENERATE CHANNEL */
var channel = PUBNUB.uuid()
, pub_key = 'demo'
, sub_key = 'demo'
, out = PUBNUB.$('pubnub-terminal-out')
, p = PUBNUB.init({ subscribe_key : 'demo', publish_key : 'demo' });
/* OPEN RECEIVE SOCKET */
p.subscribe({
channel : channel,
message : function(data) { console.log(data) },
connect : start_replay
});
/* START THE MOVIE STREAM */
function start_replay() {
p.replay({
source : 'my_channel',
destination : channel,
reverse : true
});
}
})();</script>PubNub Network offers Channel Presence which allows you to ask the question "Who's There?" and get back an answer with list of users and the occupancy count.
<div id=pubnub pub-key=demo sub-key=demo></div>
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
PUBNUB.subscribe({
channel : "hello_world", // CONNECT TO THIS CHANNEL.
message : function( message, env, channel ) {}, // RECEIVED A MESSAGE.
presence : function( message, env, channel ) { // PRESENCE
console.log( "Channel: ", channel );
console.log( "Join/Leave/Timeout: ", message.action );
console.log( "Occupancy: ", message.occupancy );
console.log( "User ID: ", message.uuid );
/* message is = {
"action" : "join",
"timestamp" : 1347946204,
"uuid" : "6e08b25f-48c0-4e94-92d0-0778a8b6013d",
"occupancy" : 1
} */
}
})
})();
</script>PubNub Network offers automatic hot-memory backfill which pulls the full queue from the message Network to provide a response filled with a compressed GZIP payload up to the maximum size of your queue length. The Default Queue size is 100 for basic PubNub Accounts. Adding backfill to a truthy value on subscribe, you can pull up to the last 100 messages off of an in-memory queue. Note that this queue may not always return 100 messages and you may instead wish to use PubNub Network History API to guarantee pulling all historical messages.
If you need to increase your queue length, contact PubNub Network at help@pubnub.com for larger queue length.
Notice that we are using backfill : true in
the pubnub.subscribe call below.
<div id=pubnub></div>
<script src=http://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js></script>
<script>(function(){
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo'
});
pubnub.subscribe({
backfill : true,
channel : 'my_channel',
callback : function(message) {
alert(JSON.stringify(message));
}
});
})();</script>Optionally PubNub offers you the full RFC 6455
Support for WebSocket Client Specification.
PubNub WebSockets enables any browser (modern or not) to support
the HTML5 WebSocket standard APIs.
Use the WebSocket Client Directly in your Browser that
Now you can use new WebSocket any time!
You will need to hit the right resource URLs. Make sure to follow the examples below.
Here is a quick example providing an easy adapter:
WebSocket = PUBNUB.ws;
var socket = new WebSocket('wss://pubsub.pubnub.com/PUB/SUB/CHANNEL');Alternatively you may directly access the PubNub WebSocket via:
var socket = new PUBNUB.ws('wss://pubsub.pubnub.com/PUB/SUB/CHANNEL')The following example opens a new WebSocket in
WSS Secure Socket Mode with 2048 Bit SSL Encryption.
<!-- Import PubNub Core Lib -->
<script src="https://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js"></script>
<!-- Use WebSocket Constructor for a New Socket Connection -->
<script>(function() {
/* 'wss://ORIGIN/PUBLISH_KEY/SUBSCRIBE_KEY/CHANNEL' */
WebSocket = PUBNUB.ws;
var socket = new WebSocket('wss://pubsub.pubnub.com/demo/demo/my_channel')
// On Message Receive
socket.onmessage = function(evt) {
console.log('socket receive');
console.log(evt.data);
}
// On Socket Close
socket.onclose = function() {
console.log('socket closed');
}
// On Error
socket.onerror = function() {
console.log('socket error');
}
// On Connection Establish
socket.onopen = function(evt) {
console.log('socket open');
// Send a Message!
socket.send('hello world!');
}
// On Send Complete
socket.onsend = function(evt) {
console.log('socket send');
console.log(evt);
}
console.log(socket)
})();</script><!-- NON-SSL Import PubNub Core Lib -->
<script src="http://pubnub.a.ssl.fastly.net/pubnub-3.5.47.min.js"></script>
<!-- NON-SSL Use WebSocket Constructor for a New Socket Connection -->
<script>(function() {
// Note "ws://" rather than "wss://"
var socket = new WebSocket('ws://pubsub.pubnub.com/demo/demo/my_channel')
})();</script>How to create a new instance of the PubNub Object directly in JavaScript.
To do this, simply follow this init example:
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
// INIT PubNub
var pubnub = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo',
origin : 'pubsub.pubnub.com',
uuid : 'myCustomUUID'
})
// LISTEN
pubnub.subscribe({
channel : "hello_world",
message : function(m){ alert(m) }
})
// SEND
pubnub.publish({
channel : "hello_world",
message : "Hi."
})
})();</script>NOTE: You do not need to use the
<div id=pubnub>DIV with this method!
Sometimes you are using a lot of Multiplexed channels which when combined
with SSL will cause slowdowns on page changes.
For single page apps, the noleave option is not required.
You do not need to use this setting for single page apps.
If you have the following combination of scenarios, then you
will want to use noleave option:
- SSL or JSONP Transports are used.
- More than
5Multiplexed Channels. - Non-single Page App.
Use the following setup commands to enable noleave.
<script src=http://cdn.pubnub.com/pubnub-3.5.47.min.js ></script>
<script>(function(){
// INIT PubNub
var pubnub = PUBNUB.init({
noleave : true,
publish_key : 'demo',
subscribe_key : 'demo'
})
// Continue as normal...
})();</script>NOTE: This will have the side affect of faster page unloads yet no explicit leaves will occur when using presence feature.
NOTE: Windowing is in favor of battery savings and throughput. The effect is more bundled messages better compression and faster response times. Windowing is a good idea most of the time.
PubNub JavaScript library includes a windowing feature that will
automatically allow the PubNub Network the window time needed
to bundle, compress and optimize messages for high-throughput.
This means that if you specify a long window, you will be able to
receive significant performance improvements and optimized performance.
With high throughput applications
(Apps that send many messages per second)
a long enough window will benefit in performance and will allow
the needed period for the PubNub Network
to order the message delivery and compress the response efficiently.
NOTE: Windowing 1000ms will allow 100 messages in a second to be bundled and compressed at optimal speeds.
var pubnub = PUBNUB.init({
windowing : 1000, // MILLISECONDS
publish_key : 'demo',
subscribe_key : 'demo'
});Windowing is a good idea! Please use it for improved network efficiency.
NOTE: The JavaScript library will automatically detect disconnects in near real-time regardless of
keepalaive.
There exists extra rare cases where keepalives are used
to detect disconnections of the network connection;
situations where a network cable was unplugged for example.
Optionally you may sacrafice bandwidth and reduce battery life
by lowering the keepalive value.
By reducing the keepalive you receive
greater precision to detect rare edge-case drops.
The Default keepalive is 60 seconds.
Reducing this value to 30 seconds will help detect
only the rare edge-case network problems
sooner under rare network disruption situations.
It is not a good idea to reduce this value lower.
If you need it lower more, you must contact PubNub first.
Again, the JavaScript library will automatically
detect disconnects in near real-time anyway,
so it is not necessary to reduce this value further.
var pubnub = PUBNUB.init({
keepalive : 30,
publish_key : 'demo',
subscribe_key : 'demo'
});The PubNub Network is a high throughput and reliable messaging service. Note however that PubNub is not a guaranteed delivery with full Read Receipt Transactions. You can however use improved designs and best practices to ensure you increase reliability. One method includes High Windowing Length which provides slight improvements.
NOTE: Higher windowing lengths allow improved message delivery.
We recommend following a few best practices to achieve high frequency of message delivery. First ensure you are checking the publish response code and re-sending the publish if an error code is returned.
There is an easy way to make sure you do not run into undelivered messages due to high frequency of published. Actually there are a few easy ways. The first option is to make sure you don't publish too quickly. Do this by limiting to one concurrent publish per channel. This is achievable by waiting for the publish response before sending another message.
Use our Elastic Message options. You should instead send a single large message rather than segment messages into small packets you manually assemble them on the receiving client.
NOTE: Turn on Elastic Message Sizes in your Customer Account: https://admin.pubnub.com/
Is it possible to ensure 100% messages are delivered? YES! The way to do this includes a Read Receipt Design Pattern. You must allow the Receiver of a message to ACKNOWLEDGE that a message was successfully received. The Sender will continuously re-send the message; with a delay between each re-send. This continues until an ACKNOWLEDGEMENT is received from the receiver.
It is important to note that the PubNub JavaScript SDK will automatically select the best transport method. However if you desire, you can change this...
If you desire, though it is not recommended, you may manually enforce JSON(P) or Flash Socket transports. It is simple to manually enforce these transport mechanisms if needed though again it is not recommended unless you are deploying on specific platforms such as Philips Embedded SmartTV or Opera Powered TV platforms which sometimes simply require certain interfaces to be enforced.
NOTE: The PubNub div is required for the Flash Socket.
<div id=pubnub flash=true></div>
<script>
var flash_socket = PUBNUB.init({
publish_key : 'demo',
subscribe_key : 'demo',
origin : 'pubsub.pubnub.com'
});
</script>This will enforce the JSON(P) Transport to be used only and will avoid all other transport methods.
NOTE: you must Exclude the PubNub div.
<script>
var pubnub = PUBNUB.init({
jsonp : true,
publish_key : 'demo',
subscribe_key : 'demo',
origin : 'pubsub.pubnub.com'
});
</script>Maintaining a plethora of JS-based clients is not easy. Even the most trivial change means altering the code across JS-based clients. This became very difficult to maintain, so we decided to build a common codebase, and wrap platform-specific wrappers around it as needed at build time. This helps us make a fix once, and have it reflected in all JS clients immediately with little or no extra effort.
Following software and tools are used:
- Jenkins
- Testswarm
- BrowserStack
- node-testswarm
- testswarm-browserstack
And a bit more detail on how it all fits together:
- Github hooks have been configured to hit Jenkins on staging pushes.
- Jenkins starts a new build upon the push.
- First mocha tests are run. If they succeed...
- Jenkins creates a job on testswarm to execute qunit tests across various browsers. Cross-browser testing is done via BrowserStack. A script runs on the server which keeps querying testswarm for the swarm state . The state defines which browsers are required by swarm. This script then spawns those browsers on BrowserStack. The browsers not required any more are killed. This way whenever a job is submitted, the script will start browsres and kill them once done.
- The job creation script keeps polling swarm for test results. If the results indicate success, the build status is set as passed... if the tests indicate failure, build status is set as failure, and mail is sent to PubNub support for further investigation.