On Mon, Mar 20, 2017 at 1:54 PM, Ayyoob Hamza <ayy...@wso2.com> wrote:
> Agree that it's better to handle this in super tenant layer due to its
> complexity, but I wonder whether this needs to be specific for
> MQTT scenarios. Because we need the same requirement for HTTP and thrift
> receivers. So for HTTP and Thrift can we have it through super tenant space
> or do we have to think of a generic solution on how to deploy the artifacts
> for the tenants.
Thrift case is different, because there is only one listener for all
tenants and we don't start different endpoints/listeners per tenant. And
the tenent flow is started, once the tenant is authenticated and sending
the events. In the case of HTTP, we do have the same problem as MQTT. In
HTTP case, there is seperate HTTP endpoints registered for different
tenants, and AFAIR those will be removed once the tenant is unloaded. So
far, we didn't have problems in the deployments as HTTP or other receivers
than thrift is used in the multi tenant case.
> In addition to recievers, we are using publishers and
> tenant-specific summarisation scripts, does these gets undeployed when the
> tenant is unloaded ?.
Summarization scripts will work, AFAIR the tasks registered for the tenants
will be still active though the tenant is unloaded, and once the trigger
has been received for the task, it will be loading the tenant and executing
the script. For the event publishers, the same issue exists, but before the
publisher gets tiggered the event should be arrived into the core, and by
that time the tenant is already loaded and hence I believe the publishers
will not be having this problem.
> *Ayyoob Hamza*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
Architecture mailing list