Mailing-List: contact issues-help@shindig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shindig.apache.org
Date: Tue, 24 Jul 2012 00:34:34 +0000 (UTC)
From: "Ryan Baxter (JIRA)" <jira@apache.org>
To: issues@shindig.apache.org
Message-ID: <1719362434.93629.1343090074933.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <202233270.26439.1340047902840.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (SHINDIG-1805) Better error handling around
 container token refreshes.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SHINDIG-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Baxter updated SHINDIG-1805:
---------------------------------

    Fix Version/s: 2.5.0-beta3
    
> Better error handling around container token refreshes.
> -------------------------------------------------------
>
>                 Key: SHINDIG-1805
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1805
>             Project: Shindig
>          Issue Type: Improvement
>            Reporter: Dan Dumont
>            Assignee: Dan Dumont
>             Fix For: 2.5.0, 2.5.0-beta3
>
>
> It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned.  The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)

--
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