You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Alexey Ghenov (JIRA)" <ji...@apache.org> on 2013/07/04 13:45:47 UTC
[jira] [Closed] (OPENMEETINGS-576) Suggestion about the tunnelling
implementation.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Ghenov closed OPENMEETINGS-576.
--------------------------------------
Resolution: Not A Problem
Fix Version/s: 3.0.0 Apache Release
Resolved by Maxim Solodovnik -
Since OM 3.0.0 rev. 1499667
Additional RTMPT port (8088 by default) is no longer required, RTMPT
communications are performed using standard Om port (5080 by default)
> Suggestion about the tunnelling implementation.
> -----------------------------------------------
>
> Key: OPENMEETINGS-576
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-576
> Project: Openmeetings
> Issue Type: New Feature
> Environment: Unix
> Reporter: Alexey Ghenov
> Priority: Minor
> Labels: newbie
> Fix For: 3.0.0 Apache Release
>
> Attachments: build.properties, build.xml, OPENMEETINGS-576
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> - proper traffic tunnelling (images and screensharing now use 5080 port, SIP applet likely uses different ports as well, while anything should be happy with 80 port);
> - performance: getting rid of Apache httpd to improve openmeetings hosting performance (Apache eats tons os megabytes - proper jetty configuration can be done as a part of tunelling task);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira