It works if the request is made to ws requests are made through port 7070.
Can you share with team what changes you made to get the app working in details? Specifically what changes you made in libs/strophe-connection-websockets.js
Yes , these are browser specific , i tested them with a normal channel release of chrome and it works , the problem is seen only in Dev channel releases ⌠and it could be fixed by
I am pretty sure, there would be a live community commiting patches and fixes for all this openfire stuff and this stuff would involve much master if you would choose a state of the art opensource community plattform an source code managment, that would allow easy partitioning and contributing.
Neither contributing is is possible for everyone on code level nor an quality issue tracker is avaiblabe, where code changes can be linked with issues.
Please move this whole stuff to github.com. Building up a repository in less than some clicks and done in some minutes. Then everyone can fork and upstream his pacthes and master can merge them after review.
Patching by comments âchange this line by this line from download link from comments number xâ wonât envovle this code fast anywhere.
Iâm just sad about this great project and stuff around has to suffer from such bad environment.
Great suggestion, but Ignite Realtime needs more developers like you to get involved more than it needs to migrate to github.com
Last time I checked, all ignite realtime projects are on SVN and linked to Jira for issue tracking. Get hold of the project owner and submit a patch if you have one.
Github.com may be the in-place at the moment, but it is a commercial organisation. Why should we leave our own hosted servers which is sponsored by Jive with all the tools we need for now and use a commercial hosted service with possible new restrictions and limits.
There is a time to use SVN and there times when Git is better. Depends on the needs of the project. Latest and greatest is not aways the best choice.