strophe-openfire-websocket

source :https://github.com/gunblues/strophe-openfire-websocket

strophe-openfire-websocket

Use strophe to connect nginx or haproxy websocket proxy

Recommand using haproxy as websocket proxy because "Connection reset by peer" happens in nginx and then connection become unavailiable, especially lots of concurrent connections or large data transfer

Especially thanks to Dele Olajide for developing the project (https://code.google.com/p/openfire-websockets/)

Installation

####Server Side (openfire):

If you use Openfire 3.10, download websockets.war (I rebuild the plugin source within openfire 3.10 source) here and put it to your openfire plugin directory
If you use Openfire 3.9.3, download websocket plugin (websockets-0.0.0.6.zip, https://code.google.com/p/openfire-websockets/downloads/list) and unzip file to your openfire plugin directory
Restart openfire server (When you use websockets.war, you have to check whether websocket.jar and Websocket.jar coexist in plugin directory. If it happens, delete Websocket.jar and restart openfire to ensure openfire load correct jar)
Visit openfire admin site and select the tab "Server" and you should see the child tab "WebSockets" and the default "Web Application Name" is ws

####Server Side (nginx): Note: if you want to connect openfire directly, just skip this step

        location /xmpp-websocket {
            proxy_pass http://yourOpenfireServer:7070/ws/server;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $host;
            tcp_nodelay on;
        }

####Server Side (haproxy): Note: if you want to connect openfire directly, just skip this step

        global
            nbproc 2
            daemon
            maxconn 4096

        defaults
            mode http
            timeout connect 5s
            timeout queue 5s
            timeout server 30s
            timeout client 5s
            timeout tunnel 1h

        frontend wss
            bind *:44443 ssl crt yourcrtfile_location
            timeout client 1h
            default_backend ws_backend

        backend ws_backend
            balance source
            option forwardfor # This sets X-Forwarded-For
            timeout queue 86400000
            timeout server 86400000
            timeout connect 86400000

            server ws1 54.223.130.159:7070 weight 1 maxconn 4096 check inter 10000

        listen stats
            bind :55688 ssl crt yourcrtfile_location
            mode http
            stats enable
            stats hide-version
            stats realm Haproxy\ Statistics
            stats uri /
            stats auth admin:adminPassword
            stats refresh 10s

####Client Side (to nginx websocket proxy (openfire)):

Checkout strophe-openfire-websocket.js and include strophe-openfire-websocket.js to your html
Add the code below to your js

    var arrURL = document.URL.split('/'),
        protocol = (arrURL[0] === 'http:' ? 'ws://' : 'wss://'),
        wsUrl = protocol + arrURL[2] + '/xmpp-websocket';

    var conn = new Openfire.Connection(wsUrl);

####Client Side (to haproxy websocket proxy (openfire)):

Checkout strophe-openfire-websocket.js and include strophe-openfire-websocket.js to your html
Add the code below to your js

    var conn = new Openfire.Connection('wss://yourHaproxyServer:44443/ws/server');

####Client Side (to openfire directly):

Checkout strophe-openfire-websocket.js and include strophe-openfire-websocket.js to your html
Add the code below to your js

    var conn = new Openfire.Connection("ws://yourOpenfireServer:7070/ws/server");

优化openfire服务器提升xmpp 效率的15个方法 http://blog.csdn.net/starcrm/article/details/52576396

1、禁用原生xmpp搜索，使组织架构、人员数据本地化保存，并使客户端数据同步服务器，降低原生xmpp搜索的iq消耗，因为搜索是im应用的频繁操作；

2、禁用roster花名册、禁用presence包通讯，企业im中的好友概念非常没必要，使用发布订阅的方式替代状态服务，见http://www.cnblogs.com/starcrm/p/5029231.html。并重写状态更新的广播：PresenceUpdateHandler中的broadcastUpdate方法。

如果想保留好友机制，建议把好友信息本地化保存，不要每次都从服务器拉取了。

3、禁用MUC的Password-Verification特性，它将造成客户端开窗前的大量iq交互。改造Roles、 Affiliations、Disco 、Querying等交互，但muc消息通讯机制可以沿用。

4、头像分离出vcard，在有头像情况下实在是太占流量了，而且openfire的缓存基本都被vcard、roster占了。头像放云里，或者搞头像服务，并且做客户端同步。

5、避免为每一种请求开发一个新iq，设计一个通用的处理iq，统一包装并解析json，简化业务处理。

6、TLS连接使用更快的算法（用ECDHE RSA-2048代替RSA-4096，而不是DHE、RC4）

7、如果使用SCRAM-SHA-1算法，服务器将哈希密码处理 (每次都发同样的salt) ，可以对 SaltedPassword 进行缓存, 将节省处理时间。

8、自动更新管理需要改进，因为openfire设计的客户端下载升级是通过自身的服务器进行，当大量客户端同时下载时一定挂。

9、尝试用redis存储缓存，让of专注于一件事：消息处理。

10、离线信息存储分库，或者用redis存。

11、不要用windows版的of，最大java内存难以大于1300MB，另外linux可更多的tcp连接。在linux下执行ulimit -n 100000设置为10万。

12、保证你重写AuthProvider的验证返回一定要快，你会发现登录时间至少提升1-2秒。

13、将登录验证的9个round trip，减少到3个round trip，这里很详细

http://blog.csdn.net/linyu19872008/article/details/24022929?utm_source=tuicool&utm_medium=referral

14、读读官方的优化方案：

http://www.igniterealtime.org/support/articles/openfire_optimization.jsp

15、另外，增加消息回执机制，解决of4.0以前的本身机制造成的丢消息风险，不清楚前几天新发布的of4.0对这个有没有改进。

欢迎补充。

今幕明 / strophe-openfire-websocket

strophe-openfire-websocket

strophe-openfire-websocket

Installation

简介

发行版

贡献者

近期动态

今幕明 / strophe-openfire-websocket .gitee-modal { width: 500px !important; }

strophe-openfire-websocket

strophe-openfire-websocket

Installation

简介

发行版

贡献者

近期动态

搜索帮助

今幕明 / strophe-openfire-websocket