Mathew,

Correct with #2 "*PubNub Plain - Send/Receive Only*" should be in fact "*PubNub 
Plain - Send/Receive OR PUB/SUB*" - Basically you have full control with 
PubNub core libarary, where as PubNub + Socket.IO you get higher level 
features while giving up some control of the data pipe to the 
Socket.IO library on PubNub.

On Tuesday, July 3, 2012 3:06:07 PM UTC-7, Stephen Blum wrote:
>
> Hi Mathew,
>
> Excellent questions regarding Socket.IO on PubNub.  To answer your 
> question, I will list the two options and describe more details with 
> pros/cons:
>
>    1. *Socket.IO + PubNub - Network Library*
>       1. You will pick this option to take advantage of a bunch of 
>       pre-built design patters such as *Multiplexing* and *Message Routing
>       * plus a *List of Users* and *Metadata* about those users.  
>       2. Some pre-built security and additional connection state details 
>       are maintained behind the scenes.  
>       3. As a result the library will consume/produce a higher volume 
> of*Control Messages
>       * than if you are using the PubNub Core Library directly.  
>       4. The benefit is some great pre-built design patters that will 
>       save you time when you build your app.
>       5. The cost is higher on message consumption/production.
>    2. *PubNub Plain - Send/Receive Only*
>       1. You will pick this if you want low level Send/Receive control.  
>       2. If you want full control of the message pipe, you will pick this 
>       option.  
>       3. Pick this option to have full control of send/receive pipeline 
>       and employ any variety of design pattern needed.
>       4. You are not locked into a design pattern up front, you can 
>       send/receive to one or many endpoints easily.
>       5. You have more control here with less out-of-the box 
>       functionality than you'd get from Socket.IO library on PubNub.
>    
>
>
>
> On Tuesday, July 3, 2012 7:52:51 AM UTC-7, Matthew O'Riordan wrote:
>>
>> Thanks for the wonderfully detailed response Stephen, but I hope you can 
>> answer one last question.
>>
>> I understand your point about Socket.io being a higher-level interface, 
>> but I am still struggling to understand a good use case for using Socket.IO 
>> with PubNub.  Perhaps I am being a bit thick.  Could you give me an example 
>> or two of where there is a good fit for Socket.IO and PubNub as opposed to 
>> just PubNub on its own?
>>
>> Matt
>>
>> On 3 Jul 2012, at 05:20, Stephen Blum wrote:
>>
>> Hi Mathew!
>>
>> You are welcome for the response.  I am happy to answer more questions.
>>
>>    1. Cross Platform AES Symmetric Key Cryptography - Read Blog 
>> Article<http://blog.pubnub.com/pubnub-adds-cross-platform-aes-symmetric-key-encryption/>
>>    1. Basically Full Round-trip Cryptography of Data (Beyond SSL) 
>>       - Though your data is encrypted as it travels through the Internet, it 
>> must 
>>       be decrypted (and re-encrypted) as it passes through the PubNub 
>> servers and 
>>       back out again. This is not a limitation of PubNub, but simply a 
>> limitation 
>>       of the way SSL works.
>>       2. In regards to the Send/Receive permissions: Exclude the *PUBLISH 
>>       KEY* in order to prevent sending of data.
>>    2. SHA256/HMAC Message Origin Signing
>>    1. This happens automatically when you include the *SECRET KEY*.
>>    3. Reliability - Globally Distributed.
>>    1. We operate in 10 Discrete Physical Locations (different 
>>       buildings).  
>>       2. The most recent EC2 outage on the East Coast was mitigated and 
>>       customers were routed to the healthy data centers.
>>    4. Socket.IO + PubNub
>>       1. PubNub is a Cloud Messaging Service (Send/Receive)
>>       2. Socket.IO is a higher-level interface that provides extra 
>>       functionality on top of a Message Bus like PubNub.
>>       3. You can think of Socket.IO like a jQuery type library that sits 
>>       on top of the base infrastructure.
>>    5. Locksetp Synchronization with Everyone on Earth.
>>    1. This means that data is replicated quickly to all devices.  For 
>>       example if a Sport Score was updated while a game was in progress, 
>> this 
>>       update would be sent as a PubNub message and all phones would be 
>> updated at 
>>       the same time; all people would see the score update at the same time.
>>       2. This type of application is perfect with PubNub Galaxy, our 
>>       Mass Fan-out service: http://www.pubnub.com/solutions/pubnub-galaxy
>>    
>> Glad to be of assistance!  Note that this thread takes us a while to 
>> check for updates.  If you want a bit faster response you can send messages 
>> to [email protected] :-)
>>
>>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to