You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Henry Saputra (Commented) (JIRA)" <ji...@apache.org> on 2012/01/12 06:05:39 UTC
[jira] [Commented] (SHINDIG-1669) Navigating to URLs in the common
container has no indication of success or failure
[ https://issues.apache.org/jira/browse/SHINDIG-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184727#comment-13184727 ]
Henry Saputra commented on SHINDIG-1669:
----------------------------------------
This needs to be reopened due to SHINDIG-1679
> Navigating to URLs in the common container has no indication of success or failure
> ----------------------------------------------------------------------------------
>
> Key: SHINDIG-1669
> URL: https://issues.apache.org/jira/browse/SHINDIG-1669
> Project: Shindig
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Ryan Baxter
> Fix For: 3.0.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When you call commoncontainer.navigateUrl if the URL cannot be reached the caller has no way of knowing if the URL was navigated successfully or not. To solve this we make a head request to the URL we are navigating to and add a callback to the API.
> It is important to note that we will not be caching the response of the head request. While this could possibly give us better performance we have no way of guaranteeing the server will still be up next time and everything may fail. This is different from the gadget case where we have the gadget XML cached on the server.
--
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