:-)
I think I meant user rest API Unreachable

At the moment we do not log them in but continue to allow work until they
do something needing a login (ie almost everything) and then they get
unauthorised responses

If the user Dbase is down there is a problem - I would suggest a cache
locally in redid but that has its own pro lens

Paul Brian
07540 456 115
paul@mikadosoftware.com
Guiding you towards Continuous Delivery of software and business value.

On 18 Mar 2013, at 18:28, Philip Schatz <notifications@github.com> wrote:

In rhaptos2/repo/auth.py:

> +    >>> u = User('ben@mikadosoftware.com')
> +    >>> u.FullName
> +    u'Benjamin Franklin'
> +
> +
> +    """
> +
> +    def __init__(self, authenticated_identifier):
> +        """initialise from a id we have had verified by third party
> +
> +        .. todo::
> +           this is stubbed out - it should always go to user
> +           dbase and lookup fromidentifer
> +
> +        .. todo::
> +           what should I do if user dbase is unavilable???

return a 503/4 with {message: "USER_DATABASE_UNAVAILABLE"}

—
Reply to this email directly or view it on
GitHub<https://github.com/Connexions/rhaptos2.repo/pull/91/files#r3417747>
.

-- 


www.mikadosoftware.com

See your software improve with every change.