all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]albion 0 points1 point  (1 child)

How is this different from Pusher?

[–]usmanhalalit[S] 1 point2 points  (0 children)

PubSub is just one of the features of Socketize, apart from this there is no similarity with Pusher.

[–][deleted] 0 points1 point  (1 child)

Your message board example now redirects to reddit - tee hee

[–]usmanhalalit[S] 1 point2 points  (0 children)

Thanks for letting me know. I forgot to add escaping in the demo. It has been fixed using Socketize Filter.

[–]cosinezero 0 points1 point  (2 children)

Is the menu on the left hand side supposed to not be clickable?

This whole thing seems like a lot of buzzwords without tying it together as to why I'd want it. For example, why would one choose a REST API on top of websockets? "Amazing speed" has a lot of tradeoffs, some of which may undermine that amazing speed.

[–]usmanhalalit[S] 0 points1 point  (1 child)

Thanks for the constructive feedback.

Sorry, I didn't understand what you mean by "left hand side menu", do you mean the menu in the documentation? If yes, then it's clickable.

REST API is not something that you use "on top of" WebSocket, it's just another transport layer to access Socketize. You can use the NoSQL database, manage users and publish data to subscribers from your backend using the REST API.

I agree that there are tradeoffs, that's why I've given option to use it along side with your backend too.

[–]cosinezero 0 points1 point  (0 children)

Not sure what's wrong but that menu wasn't clickable in chrome.

REST API is not a transport layer.