You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Marshall Shi (JIRA)" <ji...@apache.org> on 2012/08/06 09:53:02 UTC
[jira] [Created] (SHINDIG-1836) upgrade OpenAjax Hub from 2.0.5 to
2.0.7
Marshall Shi created SHINDIG-1836:
-------------------------------------
Summary: upgrade OpenAjax Hub from 2.0.5 to 2.0.7
Key: SHINDIG-1836
URL: https://issues.apache.org/jira/browse/SHINDIG-1836
Project: Shindig
Issue Type: Improvement
Components: Javascript
Affects Versions: 2.5.0-beta3
Reporter: Marshall Shi
Recent Microsoft updates patched some code that was used by the RPC layer (from the Shindig project) to do messaging on Internet Explorer 6 and 7. OpenAjax Hub 2.0.7 fixes this by disabling the broken transport layer (NIX) and falling back to the fragment identifier transport (IFPC). Some further details can be found at [1] and [2].
[1] http://openajax.org/pipermail/interop/2011q2/001261.html
[2] http://openajax.org/pipermail/interop/2011q2/001262.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SHINDIG-1836) upgrade OpenAjax Hub from 2.0.5 to
2.0.7
Posted by "Marshall Shi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Shi updated SHINDIG-1836:
----------------------------------
Attachment: OAH207.patch
patch for migrating OAH 2.0.5 to 2.0.7.
> upgrade OpenAjax Hub from 2.0.5 to 2.0.7
> ----------------------------------------
>
> Key: SHINDIG-1836
> URL: https://issues.apache.org/jira/browse/SHINDIG-1836
> Project: Shindig
> Issue Type: Improvement
> Components: Javascript
> Affects Versions: 2.5.0-beta3
> Reporter: Marshall Shi
> Attachments: OAH207.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Recent Microsoft updates patched some code that was used by the RPC layer (from the Shindig project) to do messaging on Internet Explorer 6 and 7. OpenAjax Hub 2.0.7 fixes this by disabling the broken transport layer (NIX) and falling back to the fragment identifier transport (IFPC). Some further details can be found at [1] and [2].
> [1] http://openajax.org/pipermail/interop/2011q2/001261.html
> [2] http://openajax.org/pipermail/interop/2011q2/001262.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SHINDIG-1836) upgrade OpenAjax Hub from 2.0.5 to
2.0.7
Posted by "Dan Dumont (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Dumont resolved SHINDIG-1836.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.5.0-beta4
Committed r1373834
> upgrade OpenAjax Hub from 2.0.5 to 2.0.7
> ----------------------------------------
>
> Key: SHINDIG-1836
> URL: https://issues.apache.org/jira/browse/SHINDIG-1836
> Project: Shindig
> Issue Type: Improvement
> Components: Javascript
> Affects Versions: 2.5.0-beta3
> Reporter: Marshall Shi
> Fix For: 2.5.0-beta4
>
> Attachments: OAH207.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Recent Microsoft updates patched some code that was used by the RPC layer (from the Shindig project) to do messaging on Internet Explorer 6 and 7. OpenAjax Hub 2.0.7 fixes this by disabling the broken transport layer (NIX) and falling back to the fragment identifier transport (IFPC). Some further details can be found at [1] and [2].
> [1] http://openajax.org/pipermail/interop/2011q2/001261.html
> [2] http://openajax.org/pipermail/interop/2011q2/001262.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira