Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile CRM

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

Thanks Chamalee & Lakmal! Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Senior Software Engineer | WSO2 Blog: https://medium.com/@chamilad On Tue, Jul 11, 2017 at 10:50 AM, Lakmal Warusawithana wrote: > > When dynamic GWs created, adding proper domain

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

On Tue, Jul 11, 2017 at 7:54 AM, Chamila De Alwis wrote: > +1 > > IMO users wouldn't always be willing to start with a Container Cluster > Management system and limiting this feature to a few would limit their > chances to properly make use of the feature. > > From the above

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

Hi Nuwan, Thanks for pointing that out. As I first mentioned in this thread, we will provide an extension point in this feature to support other container based management systems as well without limiting to Kubernetes and Openshift. I will take this into consideration when implementing. On Tue,

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

+1 IMO users wouldn't always be willing to start with a Container Cluster Management system and limiting this feature to a few would limit their chances to properly make use of the feature. >From the above explanation, I didn't yet understand how routing would happen in a CMS when separate

Re: [Architecture] Choosing APIs to Implement Connectors

Hi Tharuka, Sounds good. Can you explain bit about how are you planning to detect the location of the user? On Mon, Jul 10, 2017 at 11:52 PM, Tharuka wrote: > Hi All, > > We are 3rd year students of University of Jaffna, as our third year project > in Rapid

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

Hi Chamalee, Shall we not limit this feature to k8s / Openshift. IMO this is quite a useful feature for many, if we limit this to users running a full blown container management platform then we are limiting the potential of this feature. Can we provide the option where 1. If someone has

[Architecture] Choosing APIs to Implement Connectors

Hi All, We are 3rd year students of University of Jaffna, as our third year project in Rapid application development We wish do impliment esb connectors for following APIs. 1. Vk - A Social media network 2. Google Geocoding - A mapping service 3. Pushover - Messaging 4. PhotoBucket - Photo And

[Architecture] Choosing APIs to Implement Connectors

Hi All, We are 3rd year students of University of Jaffna, as our third year project in Rapid application development We wish do impliment esb connectors for following APIs. 1. Vk - A Social media network 2. Google Geocoding - A mapping service 3. Pushover - Messaging 4. PhotoBucket - Photo And

Re: [Architecture] Choosing APIs for implementing connectors

Hi, I am Kausik.I am planning to implement amoCRM API's connector for our group. It is one the API from the 5 APIs in our group. This is the description of amoCRM Amo CRM amoCRM is an online sales and relationship management service designed to help users manage and pursue sales leads. The

Re: [Architecture] Choosing APIs for implementing connectors

Hi all, We changed 2 APIs because it doesn't allow the trial version to get API access. We changed 1.Sage 2.Dotmailer For that we choosed 1.amoCRM - amoCRM is a very friendly CRM and B2B leads and sales management solution. The vendor won our *Expert’s Choice Award for 2017* as well as the

Re: [Architecture] Choosing APIs for implementing connectors

-- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149953p150157.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list

Re: [Architecture] [CARBON-TRANSPORT][CARBON-MESSAGING] Client Connector Modifications

Hi All, Original purpose of this mail was to discuss websockets implementation changes. Hence this mail :) With the new client-connector and server-connector api, it should be able to return a webscoket session upon connection establishment. Since websockets is full duplex both client and sever

Re: [Architecture] [C5] [APIM] Per API Per Gateway with Kubernetes and Openshift

Hi all, We had a design review for the per API per gateway feature today. Please find the review comments in [1]. As per the the discussion in the revew what we decide was to generate the label for the APIs where the perAPIperGateway feature is enabeld as in below format. prefix-{api-UUID} I