CODEWITHSUNDEEP
websockettornado
Abdelouahab Pp
Abdelouahab Pp

Reputation: 4450

Tornado is enough for Websocket in serverside?

sorry for my dumb question, now that i got that i must use Javascript to use Websocket, this is client-side, but what about Serverside, why do i find people talking about RabbitMQ, Stomp, SocketIO, Tornadio

in the Tornado example, no one of them exists, so i said that Tornado is enough, but i found that people use them even with Tornado, here and here.

So what do i use? and for what?

Upvotes: 1

Views: 988

Answers (1)

Igor
Igor

Reputation: 3179

Actually Tornado is a web-server and it supports web-sockets. Other things in your post are not webservers.

RabbitMQ is a message queue service, it's used to communicate between different services on the server

STOMP is a protocol to work with message queues.

Socket.IO is a framework that allows you to use websockets easily. But it requires Node.JS server on the server side. Socket.IO provides you some fallbacks if browser do not support WS protocol. Tornadio is a port of Socket.IO to Tornado. So you can use the same client framework (in web-browser) but on server-side you use Tornado instead of NodeJS.

So Tornado is enough for websockets. But if you'd like to create more complex apps you'll have to use other tools for other tasks. From your list - you can use Tornadio to deal with legacy browsers and RabbitMQ for interprocess communication on your server

Upvotes: 2

Related Questions