网络聊天应用程序 - ASP.NET/Jabber/Ajax/WCF/Comet/ReverseAjax - 面临的问题 - 寻求见解

发布于 2024-09-08 21:49:20 字数 1441 浏览 2 评论 0原文

在过去的三周里，我一直在尝试构建一个基于网络的聊天应用程序，但无论我采用何种路线（编程技术/技术）来构建它，我都面临着问题。我在下面解释了我遇到的所有问题。请提供您对此的任何见解。

ASP.NET-AJAX

第一个问题是它不是真正的实时
如果客户端每 x 秒访问一次聊天服务器（恒定时间戳），它就不会是真实的时间，除非 x 非常非常小
如果 x 非常小，例如 1 秒，并且如果有 1000 个用户同时在线，我认为这确实会严重影响聊天服务器并导致可扩展性/性能问题

WCF-Duplex< /strong>

不幸的是，我浪费了大量的时间来尝试构建一个 WCF 双工服务，该服务维护所有客户端并在需要时通过通道调用客户端。但我最近学习 WCF 双工回调不适用于 ASP.NET（因为 http 是请求和响应类型）。我按照这篇很棒的文章来构建双工服务。

Comet/ReverseAjax/HTTP 服务器推送

我对这项技术非常陌生，想知道它的扩展能力如何。在我第一次浏览此编程技术之后维基和第一篇文章关于 Alex 的 Comet 此处，我了解到客户端始终与服务器保持开放连接（长期存在的ajax调用），服务器可以使用该连接将“服务器中发生的有趣事件”推送到浏览器（客户端）。那么它的扩展能力如何呢？如果 IIS 中打开连接的最大数量超出限制或出现任何其他类似问题怎么办？

Jabber 服务器/客户端 (XMPP)

我发现网上可以看到的大多数著名聊天应用程序都在使用 Jabber。我还了解到从头开始编写 Jabber 服务器是一项乏味的任务。我有按应用程序单独存储的用户配置文件。我可以轻松地将其与 Jabber 集成吗？我可以私下托管任何开源 Jabber 服务器吗？（我见过许多开源工具可以轻松构建客户端）

非常感谢您提供的任何见解。

谢谢

NLV

原文

I've been trying to build a web based chat application for the past three weeks and i'm facing issues with whatever route (programming technique/technology) i take to build it. I've explained the issues i've experienced with all of'em below. Kindly provide whatever insights you have in this.

ASP.NET-AJAX

First issue is that it is Not Really Real Time
If client hits the chat server every x seconds (constant time stamp) it is not going to be real time unless x is very very less
If x is very small like 1 second and if there are 1000 users online at the same time i think it is really going to hammer the chat server and cause scalability/performance issues

WCF-Duplex

I unfortunately wasted considerable amount of time in this trying to build a WCF duplex service which maintains all the clients and invokes the client through the channel as and when required. But i recently learnt that WCF duplex callback wont work with ASP.NET (since http is request and respond type). I was following this great article to build a duplex service.

Comet/ReverseAjax/HTTP Server Push

I'm extremely new to this technique and wonder how well enough it can scale. After my first glance on this programming technique here in wiki and the very first article on Comet by Alex here, i learned that the client always maintains an open connection (long living ajax calls) to the server which can be used by the server to push "interesting events happening in the server" to the browser (client). So how well can it scale? What if the max no of open connections exceed in IIS or any other issues like that?

Jabber Server/Client (XMPP)

I see that most of the prominent chat applications that can be seen online are making use of Jabber. I also learned that writing a Jabber server from the scratch is a tedious task. I have separate user profile store for by application. Can i integrate that with Jabber easily? Any open source Jabber servers that i can host privately? (I've seen many open source tools to build the client easily)

Any insights provided are very much appreciated.

Thank you

NLV

分享到QQ

分享到微博