You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by "Akila (JIRA)" <ji...@apache.org> on 2015/11/11 10:47:11 UTC

[jira] [Resolved] (STRATOS-1612) Tenant Model and Complete Application SignUps Initialization Optimization

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

Akila resolved STRATOS-1612.
----------------------------
    Resolution: Fixed

Implemented in 60b801144dcb05e3664353c412bc1c3fffd7c55c

> Tenant Model and Complete Application SignUps Initialization Optimization
> -------------------------------------------------------------------------
>
>                 Key: STRATOS-1612
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1612
>             Project: Stratos
>          Issue Type: Improvement
>          Components: Messaging, Stratos Manager
>            Reporter: Akila
>            Assignee: Akila
>             Fix For: 4.1.5
>
>
> Currently Complete Tenant event and Complete Application SignUps events are published by Stratos Manager every minute to let the subscribers to initialize the current state of the tenant model and application signups model in their local instance. This causes the subscribers to wait for one minute (in the worst case) to start their standard functionality.
> We can improve this by sending the Complete Tenant and Complete Application SignUps events on demand. The idea is to introduce a new topic called "initializer" to let the subscribers to request the events.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)