Re: [Architecture] Choosing APIs to Implement Connectors

Thank you sir. Tharuka KasthuriArachchi. Department of Computer Science. University of Jaffna. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-to-Implement-Connectors-tp150163p150222.html Sent from the WSO2 Architecture mailing list archive at

Re: [Architecture] Choosing APIs to Implement Connectors

Hi Tharuka, Thx for the explanation. This looks good. On Wed, Jul 12, 2017 at 12:34 AM, Tharuka wrote: > Hello Sir. > > I think you didn't get clearly what I'm tryng to say.Here is the simple > sequence Diagram. >

Re: [Architecture] Choosing APIs to Implement Connectors

Hello Sir. I think you didn't get clearly what I'm tryng to say.Here is the simple sequence Diagram. Thank you sir. Tharuka KasthuriArachci. Department of Computer Science, University of Jaffna. -- View this message in

Re: [Architecture] Choosing APIs to Implement Connectors

Hello Sir. I think you didn't get clearly what I'm tryng to say.Here is the simple sequence Diagram. sequence_diagram.docx Thank you sir. Tharuka KasthuriArachci. Department of Computer Science, University of

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

Hi Lakmal, Ah right, with the label concept you can push one api for a particular gateway. Thanks for the clarification. Regards, /Nuwan On Tue, Jul 11, 2017 at 10:52 AM, Lakmal Warusawithana wrote: > Hi Nuwan, > > On Tue, Jul 11, 2017 at 7:27 PM, Nuwan Bandara

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

Hi Nuwan, On Tue, Jul 11, 2017 at 7:27 PM, Nuwan Bandara wrote: > Hi Chamalee > > On Tue, Jul 11, 2017 at 1:11 AM, Chamalee De Silva > wrote: > >> Hi Nuwan, >> Thanks for pointing that out. >> As I first mentioned in this thread, we will provide an extension

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

Hi Chamalee On Tue, Jul 11, 2017 at 1:11 AM, Chamalee De Silva wrote: > 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

Re: [Architecture] Choosing APIs to Implement Connectors

Hi Tharuka ​, If I understand correctly when an user ​uploads content, user gets a notification to his/her own mobile device? If not can you provide more details on the use case you are planning to implement. Maybe a simple sequence diagram may help? On Tue, Jul 11, 2017 at 5:50 PM, Tharuka

Re: [Architecture] Choosing APIs to Implement Connectors

Hello Sir, Thank you for your consideration and reply, in vk.com their is a option to allow the current location of the user when they uploading a post. we can detect their location by that method and for messaging option we use to use their last location(which uploaded their last post) as their

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 Buffer API. The following are methods which i have selected to implement. Buffer is a new and smarter way to share what you want to share on Social Media. People have

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project. I am planning to to do a connector for FollowUpBoss API. Follow Up Boss is designed for real estate teams. Their mission is to help agents follow up faster, more often, and with the leads most likely to

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

Thanks Lakmal! Got it! 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 12:05 PM, Lakmal Warusawithana wrote: > > > On Tue, Jul 11, 2017 at 11:07 AM, Chamila De

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

On Tue, Jul 11, 2017 at 11:07 AM, Chamila De Alwis wrote: > 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,

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project.I am planning to do a connector for StreakCRM API.Streak is the developer of an eponymous customer relationship management platform for Gmail.The following are methods which i have selected to implement.

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project.I am planning to do a connector for StreakCRM API.Streak is the developer of an eponymous customer relationship management platform for Gmail.The following are methods which i have selected to implement.

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] 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

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

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