You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "John Hjelmstad (JIRA)" <ji...@apache.org> on 2008/07/31 21:42:31 UTC
[jira] Created: (SHINDIG-485) Legacy IFPC packet format broken due
to serviceName no longer being in scope
Legacy IFPC packet format broken due to serviceName no longer being in scope
----------------------------------------------------------------------------
Key: SHINDIG-485
URL: https://issues.apache.org/jira/browse/SHINDIG-485
Project: Shindig
Issue Type: Bug
Components: Features (Javascript)
Reporter: John Hjelmstad
http://issues.apache.org/jira/browse/SHINDIG-410 introduced a bug whereby callIfpc(...) does not have variable "serviceName" in scope. This manifests as a JS error, only when the legacy IFPC packet format is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHINDIG-485) Legacy IFPC packet format broken due
to serviceName no longer being in scope
Posted by "John Hjelmstad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Hjelmstad resolved SHINDIG-485.
------------------------------------
Resolution: Fixed
Committed.
> Legacy IFPC packet format broken due to serviceName no longer being in scope
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-485
> URL: https://issues.apache.org/jira/browse/SHINDIG-485
> Project: Shindig
> Issue Type: Bug
> Components: Features (Javascript)
> Reporter: John Hjelmstad
> Attachments: rpc.js.serviceName-legacyProtocol-fix
>
>
> http://issues.apache.org/jira/browse/SHINDIG-410 introduced a bug whereby callIfpc(...) does not have variable "serviceName" in scope. This manifests as a JS error, only when the legacy IFPC packet format is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-485) Legacy IFPC packet format broken due
to serviceName no longer being in scope
Posted by "John Hjelmstad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Hjelmstad updated SHINDIG-485:
-----------------------------------
Attachment: rpc.js.serviceName-legacyProtocol-fix
Attached patch should resolve the issue.
> Legacy IFPC packet format broken due to serviceName no longer being in scope
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-485
> URL: https://issues.apache.org/jira/browse/SHINDIG-485
> Project: Shindig
> Issue Type: Bug
> Components: Features (Javascript)
> Reporter: John Hjelmstad
> Attachments: rpc.js.serviceName-legacyProtocol-fix
>
>
> http://issues.apache.org/jira/browse/SHINDIG-410 introduced a bug whereby callIfpc(...) does not have variable "serviceName" in scope. This manifests as a JS error, only when the legacy IFPC packet format is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-485) Legacy IFPC packet format broken
due to serviceName no longer being in scope
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618905#action_12618905 ]
Kevin Brown commented on SHINDIG-485:
-------------------------------------
I don't think you need a JIRA ticket just to fix a bug :)
> Legacy IFPC packet format broken due to serviceName no longer being in scope
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-485
> URL: https://issues.apache.org/jira/browse/SHINDIG-485
> Project: Shindig
> Issue Type: Bug
> Components: Features (Javascript)
> Reporter: John Hjelmstad
> Attachments: rpc.js.serviceName-legacyProtocol-fix
>
>
> http://issues.apache.org/jira/browse/SHINDIG-410 introduced a bug whereby callIfpc(...) does not have variable "serviceName" in scope. This manifests as a JS error, only when the legacy IFPC packet format is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-485) Legacy IFPC packet format broken
due to serviceName no longer being in scope
Posted by "John Hjelmstad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618907#action_12618907 ]
John Hjelmstad commented on SHINDIG-485:
----------------------------------------
Ha, true, but why not? :)
> Legacy IFPC packet format broken due to serviceName no longer being in scope
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-485
> URL: https://issues.apache.org/jira/browse/SHINDIG-485
> Project: Shindig
> Issue Type: Bug
> Components: Features (Javascript)
> Reporter: John Hjelmstad
> Attachments: rpc.js.serviceName-legacyProtocol-fix
>
>
> http://issues.apache.org/jira/browse/SHINDIG-410 introduced a bug whereby callIfpc(...) does not have variable "serviceName" in scope. This manifests as a JS error, only when the legacy IFPC packet format is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.