There is document on scalability from 2007 that shows 50000 users supported on version 3.2. The current release is 3.7.1. Don't forget that that also means a much slower machine than anything you are likely to run on today.
You also have to take into account what features of XMPP you will be using, but simple messaging should be able to easily handle the numbers you are referring to.
您可能会错过的唯一一件事是 Web 界面（ejabberd 有，但它相当有限），但是如果您希望通过应用程序的 Web UI 来管理事物，您将需要再考虑一下；）
The numbers you mention should be easily handled by ejabberd.
I am unsure as to how you want to "extend" ejabberd. Multi-user chat and messaging are handled fine by all servers and of course ejabberd. Additionally, if you are thinking of custom protocols, these can be written in your language of choice and connect to ejabberd as an XMPP component.
The only thing you might miss is a web interface (which ejabberd has but it's rather limited), but then again if you expect to manage things through a web UI for an application, you will need to think again ;)
if you want to go with ejabberd, you can always get support from ProcessOne. This is another plus for ejabberd, as it can be commercially supported if you want to / can afford.
With Android-Push services, you (Android developers) can send messages directly to the people who have installed your app. All you need is to include a code snippet into your app, and post to a specific URL to reach your app users, even if your app is inactive on their phone.
Feature:
Free
Free, unless you need extensive number of pushes for your app. Of course you can pay for more push and a quicker tech support.
Easy
Extremely easy to integrate into your app Super simple to push to the app: just send a URL request No C2DM limit, you don't have to have a gmail account to use the push service Cloud service, no need to setup your own push server
Effective
Low battery and network consumption on the phone Track user interaction, find out how users react to your push
发布评论
评论（4）
有多个参考资料介绍了 Openfire 在单个服务器上处理这些和大量并发用户。
2007 年的有关可扩展性的文档显示版本 3.2 支持 50000 个用户。当前版本是 3.7.1。不要忘记，这也意味着机器比您今天可能运行的任何机器都要慢得多。
您还必须考虑您将使用 XMPP 的哪些功能，但简单的消息传递应该能够轻松处理您所引用的号码。
There are several references to Openfire handling those and larger numbers of concurrent users on a single server.
There is document on scalability from 2007 that shows 50000 users supported on version 3.2. The current release is 3.7.1. Don't forget that that also means a much slower machine than anything you are likely to run on today.
You also have to take into account what features of XMPP you will be using, but simple messaging should be able to easily handle the numbers you are referring to.
ejabberd 应该可以轻松处理您提到的数字。
我不确定你想如何“扩展”ejabberd。所有服务器（当然还有 ejabberd）都能很好地处理多用户聊天和消息传递。此外，如果您正在考虑自定义协议，则可以使用您选择的语言编写这些协议并作为 XMPP 组件连接到 ejabberd。
您可能会错过的唯一一件事是 Web 界面（ejabberd 有，但它相当有限），但是如果您希望通过应用程序的 Web UI 来管理事物，您将需要再考虑一下；）
The numbers you mention should be easily handled by ejabberd.
I am unsure as to how you want to "extend" ejabberd. Multi-user chat and messaging are handled fine by all servers and of course ejabberd. Additionally, if you are thinking of custom protocols, these can be written in your language of choice and connect to ejabberd as an XMPP component.
The only thing you might miss is a web interface (which ejabberd has but it's rather limited), but then again if you expect to manage things through a web UI for an application, you will need to think again ;)
如果您想使用 ejabberd，您随时可以从 ProcessOne 获得支持。
这是 ejabberd 的另一个优点，因为如果您愿意/负担得起，它可以得到商业支持。
if you want to go with ejabberd, you can always get support from ProcessOne.
This is another plus for ejabberd, as it can be commercially supported if you want to / can afford.
Android 推送通知是一个很好的解决方案。
借助 Android-Push 服务，您（Android 开发人员）可以直接向安装了您应用程序的用户发送消息。您所需要做的就是将代码片段包含到您的应用程序中，然后发布到特定的 URL 来接触您的应用程序用户，即使您的应用程序在他们的手机上处于非活动状态也是如此。
功能：
免费
免费，除非您的应用程序需要大量推送。当然，您可以付费获得更多的推送和更快的技术支持。
简单
非常容易集成到您的应用程序中
推送到应用程序超级简单：只需发送 URL 请求
无C2DM限制，您无需拥有gmail帐户即可使用推送服务
云服务，无需搭建自己的推送服务器
有效
手机电池和网络消耗低
跟踪用户交互，了解用户对您的推送有何反应
Android Push Notification is a good solution.
With Android-Push services, you (Android developers) can send messages directly to the people who have installed your app. All you need is to include a code snippet into your app, and post to a specific URL to reach your app users, even if your app is inactive on their phone.
Feature:
Free
Free, unless you need extensive number of pushes for your app. Of course you can pay for more push and a quicker tech support.
Easy
Extremely easy to integrate into your app
Super simple to push to the app: just send a URL request
No C2DM limit, you don't have to have a gmail account to use the push service
Cloud service, no need to setup your own push server
Effective
Low battery and network consumption on the phone
Track user interaction, find out how users react to your push