Help with Node.js Redis + Backend Design Phase

[Rob]

Hi guys,

I need help with the design of a node.js socket.io chat application.  I am stuck on trying to figure out how to implement the backend storage side of things to store chat messages and have it appear as though a chat is long running or time independent.  For example two users having a chat, one may leave for say a week comeback and continue with chat as though they never left.  I am guessing that socket.io namespaces and rooms would play a part in it but am not sure as to architect the application properly to load up the room again for 1 or more users to re-join.

Platform:

- Windows Azure (storage, blobs, queues)
- Windows Azure Compute (websites, cloud service)
- Windows Azure Service Bus
- Node.js / socket.io / redis

Any help with figuring out the architectural aspects of creating a real-time global chat service would be appreciated.

[Peter Johnson]

Have a look at https://www.firebase.com

--
You received this message because you are subscribed to the Google Groups "Node.js NZ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs-nz+...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/nodejs-nz/1ffdab9b-8227-43cc-8ff0-ec0ce6f67284%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rob]

Cheers Peter I'll have a look into it.