带有websocket + node.js的聊天服务器与带有xmpp的本地客户端 [英] Chat server with websocket+node.js vs a native client with xmpp

查看:144
本文介绍了带有websocket + node.js的聊天服务器与带有xmpp的本地客户端的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在使用node.js聊天服务器V.S运行的聊天客户端之间的比较方面,我找不到任何合理的基准.使用xmpp的客户端.

I couldn't find any reasonable benchmarks regarding comparison between a chat client that runs with using node.js chat server V.S. a client that works with xmpp.

我知道node.js是异步的,据我所知xmpp也是如此.但是,我主要关心的是并发用户数量相同时的性能.

I know node.js is async and as far as I know so does xmpp . However, my main concern is performance with same amount of concurrent users.

我将需要此信息来编写android应用.希望了解您使用这两种系统的看法和优点/缺点.

I would need this information to write an android app. Would like to know your opinions and advantages/disadvantages using both systems.

提前谢谢.

推荐答案

这还取决于您编写的客户端类型:基于浏览器的客户端使用BOSH,它是HTTP上的XMPP,它使用长轮询(类似于彗星).这每30秒(取决于设置)从每个客户端至少创建一个请求,当您获得数千个客户端后,该请求就会开始累加.我很想看到对此的比较-似乎Web套接字在那里应该有优势.

It also depends on what kind of client you are writing: browser based clients use BOSH which is XMPP over HTTP, which uses long polling (similar to comet). This creates at least one request every 30 seconds (depending on settings) from each client, which starts to add up after you get a few thousand clients. I'd be interested to see a comparison on that - seems like web sockets should have an advantage there.

这篇关于带有websocket + node.js的聊天服务器与带有xmpp的本地客户端的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆