[Architecture] CEP - Largest Connected Component and Maximum Clique implementation

Hi All, We are implementing 2 Siddhi Extensions 1) Largest Connected Component and 2) Maximum Clique. Using these extensions we can identify/detect the largest connected component and the maximum clique in a (large) undirected graph. A connected component/clique could represent a community that

Re: [Architecture] [Arch] Adding CEP and ML samples to DAS distribution in a consistent way

Adding Azeez and Sameera to get their feedback. I think this is not limited to DAS. (e.g. same happen when we ship DS with AS etc). reference to DAS, I am more and more convinced we should do one distribution and make ML and CEP profiles. But that is a fight for later. --Srinath On Mon, Aug 8,

Re: [Architecture] Fwd: Implementation of Websockets for API Manager

On Wed, Aug 10, 2016 at 10:45 AM, Shafreen Anfar wrote: > > On Tue, Aug 9, 2016 at 11:26 AM, Nuwan Dias wrote: > >> >> >> On Tue, Aug 9, 2016 at 11:09 AM, Shafreen Anfar >> wrote: >> >>> Hi All, >>> >>> IMO, we should not try to handle OAuth 2 scenario at websockets >>> handshake. Because webso

[Architecture] [Dev] WSO2 Message Broker 3.2.0-M2 Released !

Hi All, The WSO2 Message Broker team is pleased to announce the 2nd milestone release of WSO2 Message Broker (MB) 3.2.0. Source & binary distribution files of WSO2 Message Broker : Runtime : https://github.com/wso2/product-mb/releases/tag/v3.2.0-M2 Analytics : https://github.c

Re: [Architecture] Fwd: Implementation of Websockets for API Manager

On Tue, Aug 9, 2016 at 11:26 AM, Nuwan Dias wrote: > > > On Tue, Aug 9, 2016 at 11:09 AM, Shafreen Anfar wrote: > >> Hi All, >> >> IMO, we should not try to handle OAuth 2 scenario at websockets >> handshake. Because websockets handshake is a transport layer thing whereas >> OAuth 2 is more like

Re: [Architecture] Concurrency controlling for API Manager

Hi All IMO the key benefit of implementing ETag would be to support caching and to reduce the server load. Concurrency control would be a added benefit otherwise which can be implemented by having "Last-Modified" and "If-Umodified-Since" in a simpler way. Given above. 1. If we hash the full paylo

Re: [Architecture] [Dev] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

Based on the chat with Johann he suggested to support claims at event publisher. @Indunil, can you get the full requirements and update the thread. Regards Suho On Mon, Aug 1, 2016 at 11:24 PM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > > > On Mon, Aug 1, 2016 at 8:38 PM, Indunil

Re: [Architecture] [APIM] [EMM] Adding multiple scopes to a single API resource endpoint

If you do that and depend on OAuth 2.0 scopes to determine the data to be returned from your Application, you're basically tying a core Application logic to the security protocol of the API. What happens if you later decide to remove OAuth and use some other protocol to secure your API? In my view

[Architecture] [Dev] WSO2 Identity Server 5.3.0 Milestone 4 Released..!!

​​ *WSO2 Identity Server 5.3.0 Milestone 4 Released..!!* The WSO2 Identity Server team is pleased to announce the 4th Milestone of WSO2 Identity Server 5.3.0. You can download this distribution from https://github.com/wso2/product-is/releases/tag/v5.3.0-m4 Following list contains all the features

Re: [Architecture] [APIM] [EMM] Adding multiple scopes to a single API resource endpoint

Hi Nuwan, The responsibility of this authorization check could be assigned to either one of the layers that you have mentioned. Currently, we have assigned this responsibility to API layer of the backend system. Cheers, Dilan. *Dilan U. Ariyaratne* Senior Software Engineer WSO2 Inc.

Re: [Architecture] Concurrency controlling for API Manager

Sanjeewa, yes, Level 3 of the Richardson Maturity Model is about HATEOAS. And we agreed to not support HATEOAS because there are no accepted best practices around that, especially, how clients would make effective use of it. Level 2 is about proper use of HTTP methods, which *includes* use of app

Re: [Architecture] RDBMS based coordinator election algorithm for MB

Great! .. Cheers, Anjana. On Tue, Aug 9, 2016 at 1:49 PM, Asanka Abeyweera wrote: > Hi Anjana, > > Thank you for the suggestion. We have already done a similar thing. We > have added a backoff time after creating the leader entry and check if the > leader entry is the entry created by self befo

Re: [Architecture] Concurrency controlling for API Manager

On Tue, Aug 9, 2016 at 2:26 PM, Malintha Amarasinghe wrote: > Hi Sineth, > > We cannot use ESB's cache mediator directly in REST API as it is a > completely different context (Cache mediator is used in Synapse Gateway > level and REST API is based on Apache CXF which is a web application). But >

Re: [Architecture] Concurrency controlling for API Manager

Hi Sineth, We cannot use ESB's cache mediator directly in REST API as it is a completely different context (Cache mediator is used in Synapse Gateway level and REST API is based on Apache CXF which is a web application). But we can look into its implementation and see how it's done. It seems in S

Re: [Architecture] RDBMS based coordinator election algorithm for MB

Hi Anjana, Thank you for the suggestion. We have already done a similar thing. We have added a backoff time after creating the leader entry and check if the leader entry is the entry created by self before informing the leader change. On Tue, Aug 9, 2016 at 12:27 PM, Anjana Fernando wrote: > I

[Architecture] Visual Editor for NEL : Current work and path forward

Hi, As part of Next Gen Tooling based on web platform, we are currently working on an interactive visual editor for next generation ESB language (NEL). You can find the initial work at [2 ][3