Look OK as long as we do not make non-tenant case complicated.
When you list streams, would you see the tenantA part? what happen when
people debug things?
What would happen with super tenant?
--Srinath
On Wed, Jan 22, 2014 at 6:10 PM, Mohanadarshan Vivekanandalingam
mo...@wso2.com wrote:
Hi All,
Thanks for your ideas...
Look OK as long as we do not make non-tenant case complicated.
Yes, I think it will not make much complicate..
When you list streams, would you see the tenantA part? what happen when
people debug things?
What would happen with super tenant?
Yes.. Since
This may be different from the current context but may be important if we
are thinking back to re-implement the data-bridge in a better way.
In the current data publishing, the publisher side should be authenticated
with the BAM/CEP side username and password. This is asking for username
and
Hi Mohan,
*Solution*
If we make the streamId unique across multiple tenants then we can
overcome this issue. That means prefixing the tenant domain with streamId.
For example - If Tenant-A (tenant domain is tenantA) created a stream
called testStream with version 1.0.0 then streamId is
Hi All,
As you already knew that CEP BAM works based on stream concept. We are
defining the streams in a strict format. Here streams are uniquely
identified by combination of StreamName and Stream Version (Simply
StreamId). If an event comes to CEP or BAM, we check the streamId of the
event and
