Re: [Architecture] Selecting a Javascript markdown library for APIM 2.x - In-line Documents
Hi Jerad, Thank you. No, we are currently not using Uikit in the APIM AFAIK Best Regards, *Varuni Punchihewa* Software Engineer - Intern | *WSO2* *Tel:* +94 71 699 5861 <http://wso2.com/signature> On Sat, Feb 16, 2019 at 6:05 PM Jerad Rutnam wrote: > Hi Varuni, > > I think anyway for react version (APIM v3.xx) you will have to use a react > markdown library. Probably the one [1] which Chamin shared. > But for APIM v2.xx better choose a different JS library. I have seen the > showdown [2] and markdown-it [3] using widely. > Also check GitHub markdown parser [4] as well. Which is their kramdown > parser. > > Are we using UIKit already anywhere? > > [1] https://github.com/rexxars/react-markdown > [2] https://github.com/showdownjs/showdown > [3] https://github.com/markdown-it/markdown-it > [4] https://github.com/github/markup > > Cheers! > > On Sat, Feb 16, 2019 at 10:21 AM Varuni Punchihewa > wrote: > >> Hi Jerad, >> >> Currently, when you are adding a New Document to the API in the Publisher >> (v2.x), you can only give Inline, URL and File as the source type. It >> doesn't have a mechanism to add markdown (md) docs. >> This is to give that support to the API Publisher. >> >> Best Regards, >> *Varuni Punchihewa* >> Software Engineer - Intern | *WSO2* >> *Tel:* +94 71 699 5861 >> <http://wso2.com/signature> >> >> >> On Sat, Feb 16, 2019 at 10:07 AM Jerad Rutnam wrote: >> >>> Hi Varuni, >>> >>> Can you also explain where we need it and what are we trying to achieve >>> by giving markdown support in v2.xx ? Because for react we already have one. >>> >>> Cheers! >>> >>> On Sat, Feb 16, 2019 at 8:42 AM Varuni Punchihewa >>> wrote: >>> >>>> Hi Chamin, >>>> >>>> We had a look at the react-markdown library but prefer a javascript >>>> library more to include inside the jaggery in 2.x >>>> >>>> Best Regards, >>>> >>>> *Varuni Punchihewa* >>>> Software Engineer - Intern | *WSO2* >>>> *Tel:* +94 71 699 5861 >>>> <http://wso2.com/signature> >>>> >>>> >>>> On Fri, Feb 15, 2019 at 8:15 PM Chamin Dias wrote: >>>> >>>>> Hi, >>>>> >>>>> We had somewhat similar requirement few months ago and we decided to >>>>> choose this library. <https://github.com/rexxars/react-markdown> Are >>>>> you trying to do this using react? You can find the discussion thread >>>>> here >>>>> <http://wso2-oxygen-tank.10903.n7.nabble.com/Selecting-a-react-markdown-library-for-APIM-3-0-0-In-line-Documents-td158834.html#a158847> >>>>> . >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> On Fri, Feb 15, 2019 at 5:41 PM Varuni Punchihewa >>>>> wrote: >>>>> >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> *Varuni Punchihewa* >>>>>> Software Engineer - Intern | *WSO2* >>>>>> *Tel:* +94 71 699 5861 >>>>>> <http://wso2.com/signature> >>>>>> >>>>>> >>>>>> On Fri, Feb 15, 2019 at 5:29 PM Varuni Punchihewa >>>>>> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I have been working on giving the markdown support for APIM 2.x. and >>>>>>> the library I have planned to use was "htmleditor" in uikit library >>>>>>> [1]. >>>>>>> But found out recently that there was an XSS threat using this >>>>>>> library and they have also dropped the support for latest versions >>>>>>> telling >>>>>>> that it was out of their scope. >>>>>>> >>>>>>> Would like to know any suggestions for a good JavaScript markdown >>>>>>> editor. Please share if you have any suggestions. >>>>>>> >>>>>>> [1] https://getuikit.com/v2/docs/htmleditor.html >>>>>>> >>>>>>> Thank you and Best Regards, >>>>>>> >>>>>>> *Varuni Punchihewa* >>>>>>> Software Engineer - Intern | *WSO2* >>>>>>> *Tel:* +94 71 699 5861 >>>>>>> <http://wso2.com/signature> >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Chamin Dias >>>>> Mobile : 0716097455 >>>>> Email : cham...@wso2.com >>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>> >>>>> >>> >>> -- >>> *Jerad Rutnam* >>> *Senior Software Engineer* >>> >>> WSO2 Inc. >>> lean | enterprise | middleware >>> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com >>> >>> <https://wso2.com/signature> >>> >> > > -- > *Jerad Rutnam* > *Senior Software Engineer* > > WSO2 Inc. > lean | enterprise | middleware > M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com > > <https://wso2.com/signature> > ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Selecting a Javascript markdown library for APIM 2.x - In-line Documents
Hi Jerad, Currently, when you are adding a New Document to the API in the Publisher (v2.x), you can only give Inline, URL and File as the source type. It doesn't have a mechanism to add markdown (md) docs. This is to give that support to the API Publisher. Best Regards, *Varuni Punchihewa* Software Engineer - Intern | *WSO2* *Tel:* +94 71 699 5861 <http://wso2.com/signature> On Sat, Feb 16, 2019 at 10:07 AM Jerad Rutnam wrote: > Hi Varuni, > > Can you also explain where we need it and what are we trying to achieve by > giving markdown support in v2.xx ? Because for react we already have one. > > Cheers! > > On Sat, Feb 16, 2019 at 8:42 AM Varuni Punchihewa > wrote: > >> Hi Chamin, >> >> We had a look at the react-markdown library but prefer a javascript >> library more to include inside the jaggery in 2.x >> >> Best Regards, >> >> *Varuni Punchihewa* >> Software Engineer - Intern | *WSO2* >> *Tel:* +94 71 699 5861 >> <http://wso2.com/signature> >> >> >> On Fri, Feb 15, 2019 at 8:15 PM Chamin Dias wrote: >> >>> Hi, >>> >>> We had somewhat similar requirement few months ago and we decided to >>> choose this library. <https://github.com/rexxars/react-markdown> Are >>> you trying to do this using react? You can find the discussion thread >>> here >>> <http://wso2-oxygen-tank.10903.n7.nabble.com/Selecting-a-react-markdown-library-for-APIM-3-0-0-In-line-Documents-td158834.html#a158847> >>> . >>> >>> Thanks. >>> >>> >>> On Fri, Feb 15, 2019 at 5:41 PM Varuni Punchihewa >>> wrote: >>> >>>> >>>> Best Regards, >>>> >>>> *Varuni Punchihewa* >>>> Software Engineer - Intern | *WSO2* >>>> *Tel:* +94 71 699 5861 >>>> <http://wso2.com/signature> >>>> >>>> >>>> On Fri, Feb 15, 2019 at 5:29 PM Varuni Punchihewa >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have been working on giving the markdown support for APIM 2.x. and >>>>> the library I have planned to use was "htmleditor" in uikit library >>>>> [1]. >>>>> But found out recently that there was an XSS threat using this library >>>>> and they have also dropped the support for latest versions telling that it >>>>> was out of their scope. >>>>> >>>>> Would like to know any suggestions for a good JavaScript markdown >>>>> editor. Please share if you have any suggestions. >>>>> >>>>> [1] https://getuikit.com/v2/docs/htmleditor.html >>>>> >>>>> Thank you and Best Regards, >>>>> >>>>> *Varuni Punchihewa* >>>>> Software Engineer - Intern | *WSO2* >>>>> *Tel:* +94 71 699 5861 >>>>> <http://wso2.com/signature> >>>>> >>>> >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : cham...@wso2.com >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> > > -- > *Jerad Rutnam* > *Senior Software Engineer* > > WSO2 Inc. > lean | enterprise | middleware > M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com > > <https://wso2.com/signature> > ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Selecting a Javascript markdown library for APIM 2.x - In-line Documents
Hi Chamin, We had a look at the react-markdown library but prefer a javascript library more to include inside the jaggery in 2.x Best Regards, *Varuni Punchihewa* Software Engineer - Intern | *WSO2* *Tel:* +94 71 699 5861 <http://wso2.com/signature> On Fri, Feb 15, 2019 at 8:15 PM Chamin Dias wrote: > Hi, > > We had somewhat similar requirement few months ago and we decided to > choose this library. <https://github.com/rexxars/react-markdown> Are you > trying to do this using react? You can find the discussion thread here > <http://wso2-oxygen-tank.10903.n7.nabble.com/Selecting-a-react-markdown-library-for-APIM-3-0-0-In-line-Documents-td158834.html#a158847> > . > > Thanks. > > > On Fri, Feb 15, 2019 at 5:41 PM Varuni Punchihewa > wrote: > >> >> Best Regards, >> >> *Varuni Punchihewa* >> Software Engineer - Intern | *WSO2* >> *Tel:* +94 71 699 5861 >> <http://wso2.com/signature> >> >> >> On Fri, Feb 15, 2019 at 5:29 PM Varuni Punchihewa >> wrote: >> >>> Hi all, >>> >>> I have been working on giving the markdown support for APIM 2.x. and the >>> library I have planned to use was "htmleditor" in uikit library [1]. >>> But found out recently that there was an XSS threat using this library >>> and they have also dropped the support for latest versions telling that it >>> was out of their scope. >>> >>> Would like to know any suggestions for a good JavaScript markdown >>> editor. Please share if you have any suggestions. >>> >>> [1] https://getuikit.com/v2/docs/htmleditor.html >>> >>> Thank you and Best Regards, >>> >>> *Varuni Punchihewa* >>> Software Engineer - Intern | *WSO2* >>> *Tel:* +94 71 699 5861 >>> <http://wso2.com/signature> >>> >> > > -- > Chamin Dias > Mobile : 0716097455 > Email : cham...@wso2.com > LinkedIn : https://www.linkedin.com/in/chamindias > > ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Selecting a Javascript markdown library for APIM 2.x - In-line Documents
Best Regards, *Varuni Punchihewa* Software Engineer - Intern | *WSO2* *Tel:* +94 71 699 5861 <http://wso2.com/signature> On Fri, Feb 15, 2019 at 5:29 PM Varuni Punchihewa wrote: > Hi all, > > I have been working on giving the markdown support for APIM 2.x. and the > library I have planned to use was "htmleditor" in uikit library [1]. > But found out recently that there was an XSS threat using this library and > they have also dropped the support for latest versions telling that it was > out of their scope. > > Would like to know any suggestions for a good JavaScript markdown editor. > Please share if you have any suggestions. > > [1] https://getuikit.com/v2/docs/htmleditor.html > > Thank you and Best Regards, > > *Varuni Punchihewa* > Software Engineer - Intern | *WSO2* > *Tel:* +94 71 699 5861 > <http://wso2.com/signature> > ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Selecting a Javascript markdown library for APIM 2.x - In-line Documents
Hi all, I have been working on giving the markdown support for APIM 2.x. and the library I have planned to use was "htmleditor" in uikit library [1]. But found out recently that there was an XSS threat using this library and they have also dropped the support for latest versions telling that it was out of their scope. Would like to know any suggestions for a good JavaScript markdown editor. Please share if you have any suggestions. [1] https://getuikit.com/v2/docs/htmleditor.html Thank you and Best Regards, *Varuni Punchihewa* Software Engineer - Intern | *WSO2* *Tel:* +94 71 699 5861 <http://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway
Hi Frank,
Yes, you are correct. It actually should be the other way around where
HTTP/2 should have a low response time compared to the HTTP. As I have been
informed, there is an issue in that test case which leads to a downgrade of
performance, and they have not fixed it yet.
I'll look into this further and get back to you soon.
Best Regards,
*Varuni Punchihewa*
Software Engineer - Intern | *WSO2*
*Tel:* +94 71 699 5861
<http://wso2.com/signature>
On Sat, Jan 12, 2019 at 7:07 PM Frank Leymann wrote:
> Hi Varuni,
>
> thanks a lot! Do read it correct that HTTP2 has worse response time than
> HTTP? Although many people claim the opposite...
>
> Best regards,
> Frank
>
>
>
>
> Am Sa., 12. Jan. 2019 um 03:55 Uhr schrieb Varuni Punchihewa <
> varu...@wso2.com>:
>
>> Hi Frank,
>>
>> Here the server is written in Ballerina and you can find the Ballerina
>> performance summary in,
>> [1]
>> https://github.com/ballerina-platform/ballerina-lang/blob/master/performance/benchmarks/summary.md
>>
>> Best Regards,
>>
>> *Varuni Punchihewa*
>> Software Engineer - Intern | *WSO2*
>> *Tel:* +94 71 699 5861
>> <http://wso2.com/signature>
>>
>>
>> On Fri, Dec 21, 2018 at 4:59 PM Frank Leymann wrote:
>>
>>> +1 - I am eager to see this :-)
>>>
>>> Are we running a performance comparison between HTTP 1.1 and HTTP/2?
>>>
>>> Best regards,
>>> Frank
>>>
>>>
>>>
>>>
>>> Am Fr., 21. Dez. 2018 um 05:25 Uhr schrieb Nuwan Dias :
>>>
>>>>
>>>>
>>>> On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda
>>>> wrote:
>>>>
>>>>> Can you create document explaining this feature in detail with
>>>>> possible user scenarios. It would be great if we can have some test
>>>>> artifacts as well.
>>>>>
>>>>
>>>> +1. Let's create a GDoc and share please.
>>>>
>>>>>
>>>>> Thanks,
>>>>> sanjeewa.
>>>>>
>>>>> On Thu, Dec 20, 2018 at 3:38 PM Varuni Punchihewa
>>>>> wrote:
>>>>>
>>>>>> Hi Sanjeewa,
>>>>>>
>>>>>> There's no effect to ballerina filters from setting the http version
>>>>>> to 2.0. But the connection established via the client and the
>>>>>> microgateway
>>>>>> and microgateway with the backend would be more efficient and fast due to
>>>>>> the features like header compression, it's full multiplexed nature etc.
>>>>>> Furthermore, we won't be using the server push feature in the
>>>>>> microgateway
>>>>>> since there's no much use cases of it with the microgateway.
>>>>>>
>>>>>> Thank you
>>>>>> Best Regards,
>>>>>>
>>>>>> *Varuni Punchihewa*
>>>>>> Intern - Software Engineering | *WSO2*
>>>>>> *Tel:* +94 71 699 5861
>>>>>> <http://wso2.com/signature>
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda <
>>>>>> sanje...@wso2.com> wrote:
>>>>>>
>>>>>>> Can you please explain how are we planning to go ahead with this
>>>>>>> feature? Even now with ballerina we can create http2 client endpoint or
>>>>>>> server endpoint with http2 follows.
>>>>>>> If we do same now how will it work with existing filters?
>>>>>>>
>>>>>>> endpoint http:Listener testEP {
>>>>>>> port: 9095,
>>>>>>> httpVersion: "2.0"
>>>>>>> };
>>>>>>>
>>>>>>> Thanks,
>>>>>>> sanjeewa.
>>>>>>>
>>>>>>> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all!
>>>>>>>> Please find my project description and the design as below.
>>>>>>>>
>>>>>>>> *Project description*
>>>>>>>>
>>>>>>>> The WSO2 API Microgateway currently supports only http and https as
>>>>>>>> the incoming and outgoing transport protocols. This project is for
>&g
Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway
Hi all,
Please find the documentation for the above feature attached herewith.
[1]
https://docs.google.com/document/d/1H4_-IfyPcC1UcIgWNwFnnYRuVFo-TKPB2lUx3we0t74/edit?usp=sharing
Best Regards,
*Varuni Punchihewa*
Software Engineer - Intern | *WSO2*
*Tel:* +94 71 699 5861
<http://wso2.com/signature>
On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda
wrote:
> Can you create document explaining this feature in detail with possible
> user scenarios. It would be great if we can have some test artifacts as
> well.
>
> Thanks,
> sanjeewa.
>
> On Thu, Dec 20, 2018 at 3:38 PM Varuni Punchihewa
> wrote:
>
>> Hi Sanjeewa,
>>
>> There's no effect to ballerina filters from setting the http version to
>> 2.0. But the connection established via the client and the microgateway and
>> microgateway with the backend would be more efficient and fast due to the
>> features like header compression, it's full multiplexed nature etc.
>> Furthermore, we won't be using the server push feature in the microgateway
>> since there's no much use cases of it with the microgateway.
>>
>> Thank you
>> Best Regards,
>>
>> *Varuni Punchihewa*
>> Intern - Software Engineering | *WSO2*
>> *Tel:* +94 71 699 5861
>> <http://wso2.com/signature>
>>
>>
>> On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda
>> wrote:
>>
>>> Can you please explain how are we planning to go ahead with this
>>> feature? Even now with ballerina we can create http2 client endpoint or
>>> server endpoint with http2 follows.
>>> If we do same now how will it work with existing filters?
>>>
>>> endpoint http:Listener testEP {
>>> port: 9095,
>>> httpVersion: "2.0"
>>> };
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa
>>> wrote:
>>>
>>>> Hi all!
>>>> Please find my project description and the design as below.
>>>>
>>>> *Project description*
>>>>
>>>> The WSO2 API Microgateway currently supports only http and https as the
>>>> incoming and outgoing transport protocols. This project is for enabling it
>>>> to support HTTP2 for both incoming and outgoing message flows. We need to
>>>> evaluate the use of OAuth2.0, and rate limiting capabilities on the current
>>>> Microgateway and see how this impacts the move to HTTP2.
>>>>
>>>> *Solution Design*
>>>>
>>>>- Supporting the messages received by the microgateway from the
>>>>clients, by both HTTP/1.1 and HTTP/2.0 protocols
>>>>- All the communication that happen between the Microgateway and
>>>>the Back end service will support HTTP/2.0 (The maximum version
>>>> supported
>>>>is set to 2.0. In case if it supports only 1.1, then it will be backward
>>>>compatible to 1.1 and would not be a problem to communications)
>>>>
>>>> Best Regards,
>>>>
>>>> *Varuni Punchihewa*
>>>> Intern - Software Engineering | *WSO2*
>>>>
>>>> *Tel:* +94 71 699 5861
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>
>>>
>>> --
>>> *Sanjeewa Malalgoda*
>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>>> <https://medium.com/@sanjeewa190>
>>>
>>> GET INTEGRATION AGILE <https://wso2.com/signature>
>>> Integration Agility for Digitally Driven Business
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>
> --
> *Sanjeewa Malalgoda*
> Software Architect | Associate Director, Engineering - WSO2 Inc.
> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
> <http://sanjeewamalalgoda.blogspot.com>, Medium
> <https://medium.com/@sanjeewa190>
>
> GET INTEGRATION AGILE <https://wso2.com/signature>
> Integration Agility for Digitally Driven Business
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway
Hi Frank,
Here the server is written in Ballerina and you can find the Ballerina
performance summary in,
[1]
https://github.com/ballerina-platform/ballerina-lang/blob/master/performance/benchmarks/summary.md
Best Regards,
*Varuni Punchihewa*
Software Engineer - Intern | *WSO2*
*Tel:* +94 71 699 5861
<http://wso2.com/signature>
On Fri, Dec 21, 2018 at 4:59 PM Frank Leymann wrote:
> +1 - I am eager to see this :-)
>
> Are we running a performance comparison between HTTP 1.1 and HTTP/2?
>
> Best regards,
> Frank
>
>
>
>
> Am Fr., 21. Dez. 2018 um 05:25 Uhr schrieb Nuwan Dias :
>
>>
>>
>> On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda
>> wrote:
>>
>>> Can you create document explaining this feature in detail with possible
>>> user scenarios. It would be great if we can have some test artifacts as
>>> well.
>>>
>>
>> +1. Let's create a GDoc and share please.
>>
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Thu, Dec 20, 2018 at 3:38 PM Varuni Punchihewa
>>> wrote:
>>>
>>>> Hi Sanjeewa,
>>>>
>>>> There's no effect to ballerina filters from setting the http version to
>>>> 2.0. But the connection established via the client and the microgateway and
>>>> microgateway with the backend would be more efficient and fast due to the
>>>> features like header compression, it's full multiplexed nature etc.
>>>> Furthermore, we won't be using the server push feature in the microgateway
>>>> since there's no much use cases of it with the microgateway.
>>>>
>>>> Thank you
>>>> Best Regards,
>>>>
>>>> *Varuni Punchihewa*
>>>> Intern - Software Engineering | *WSO2*
>>>> *Tel:* +94 71 699 5861
>>>> <http://wso2.com/signature>
>>>>
>>>>
>>>> On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda
>>>> wrote:
>>>>
>>>>> Can you please explain how are we planning to go ahead with this
>>>>> feature? Even now with ballerina we can create http2 client endpoint or
>>>>> server endpoint with http2 follows.
>>>>> If we do same now how will it work with existing filters?
>>>>>
>>>>> endpoint http:Listener testEP {
>>>>> port: 9095,
>>>>> httpVersion: "2.0"
>>>>> };
>>>>>
>>>>> Thanks,
>>>>> sanjeewa.
>>>>>
>>>>> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa
>>>>> wrote:
>>>>>
>>>>>> Hi all!
>>>>>> Please find my project description and the design as below.
>>>>>>
>>>>>> *Project description*
>>>>>>
>>>>>> The WSO2 API Microgateway currently supports only http and https as
>>>>>> the incoming and outgoing transport protocols. This project is for
>>>>>> enabling
>>>>>> it to support HTTP2 for both incoming and outgoing message flows. We need
>>>>>> to evaluate the use of OAuth2.0, and rate limiting capabilities on the
>>>>>> current Microgateway and see how this impacts the move to HTTP2.
>>>>>>
>>>>>> *Solution Design*
>>>>>>
>>>>>>- Supporting the messages received by the microgateway from the
>>>>>>clients, by both HTTP/1.1 and HTTP/2.0 protocols
>>>>>>- All the communication that happen between the Microgateway and
>>>>>>the Back end service will support HTTP/2.0 (The maximum version
>>>>>> supported
>>>>>>is set to 2.0. In case if it supports only 1.1, then it will be
>>>>>> backward
>>>>>>compatible to 1.1 and would not be a problem to communications)
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> *Varuni Punchihewa*
>>>>>> Intern - Software Engineering | *WSO2*
>>>>>>
>>>>>> *Tel:* +94 71 699 5861
>>>>>> ___
>>>>>> Architecture mailing list
>>>>>> Architecture@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>&
Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway
Will do.
Best Regards,
*Varuni Punchihewa*
Software Engineer - Intern | *WSO2*
*Tel:* +94 71 699 5861
<http://wso2.com/signature>
On Fri, Dec 21, 2018 at 9:54 AM Nuwan Dias wrote:
>
>
> On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda
> wrote:
>
>> Can you create document explaining this feature in detail with possible
>> user scenarios. It would be great if we can have some test artifacts as
>> well.
>>
>
> +1. Let's create a GDoc and share please.
>
>>
>> Thanks,
>> sanjeewa.
>>
>> On Thu, Dec 20, 2018 at 3:38 PM Varuni Punchihewa
>> wrote:
>>
>>> Hi Sanjeewa,
>>>
>>> There's no effect to ballerina filters from setting the http version to
>>> 2.0. But the connection established via the client and the microgateway and
>>> microgateway with the backend would be more efficient and fast due to the
>>> features like header compression, it's full multiplexed nature etc.
>>> Furthermore, we won't be using the server push feature in the microgateway
>>> since there's no much use cases of it with the microgateway.
>>>
>>> Thank you
>>> Best Regards,
>>>
>>> *Varuni Punchihewa*
>>> Intern - Software Engineering | *WSO2*
>>> *Tel:* +94 71 699 5861
>>> <http://wso2.com/signature>
>>>
>>>
>>> On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda
>>> wrote:
>>>
>>>> Can you please explain how are we planning to go ahead with this
>>>> feature? Even now with ballerina we can create http2 client endpoint or
>>>> server endpoint with http2 follows.
>>>> If we do same now how will it work with existing filters?
>>>>
>>>> endpoint http:Listener testEP {
>>>> port: 9095,
>>>> httpVersion: "2.0"
>>>> };
>>>>
>>>> Thanks,
>>>> sanjeewa.
>>>>
>>>> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa
>>>> wrote:
>>>>
>>>>> Hi all!
>>>>> Please find my project description and the design as below.
>>>>>
>>>>> *Project description*
>>>>>
>>>>> The WSO2 API Microgateway currently supports only http and https as
>>>>> the incoming and outgoing transport protocols. This project is for
>>>>> enabling
>>>>> it to support HTTP2 for both incoming and outgoing message flows. We need
>>>>> to evaluate the use of OAuth2.0, and rate limiting capabilities on the
>>>>> current Microgateway and see how this impacts the move to HTTP2.
>>>>>
>>>>> *Solution Design*
>>>>>
>>>>>- Supporting the messages received by the microgateway from the
>>>>>clients, by both HTTP/1.1 and HTTP/2.0 protocols
>>>>>- All the communication that happen between the Microgateway and
>>>>>the Back end service will support HTTP/2.0 (The maximum version
>>>>> supported
>>>>>is set to 2.0. In case if it supports only 1.1, then it will be
>>>>> backward
>>>>>compatible to 1.1 and would not be a problem to communications)
>>>>>
>>>>> Best Regards,
>>>>>
>>>>> *Varuni Punchihewa*
>>>>> Intern - Software Engineering | *WSO2*
>>>>>
>>>>> *Tel:* +94 71 699 5861
>>>>> ___
>>>>> Architecture mailing list
>>>>> Architecture@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>
>>>>
>>>> --
>>>> *Sanjeewa Malalgoda*
>>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>>>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>>>> <https://medium.com/@sanjeewa190>
>>>>
>>>> GET INTEGRATION AGILE <https://wso2.com/signature>
>>>> Integration Agility for Digitally Driven Business
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>> <https://medium.com/@sanjeewa190>
>>
>> GET INTEGRATION AGILE <https://wso2.com/signature>
>> Integration Agility for Digitally Driven Business
>>
>
>
> --
> *Nuwan Dias* | Director | WSO2 Inc.
> (m) +94 777 775 729 | (e) nuw...@wso2.com
> [image: Signature.jpg]
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Solution Design : Support for HTTP2 on the Microgateway
Hi Sanjeewa,
There's no effect to ballerina filters from setting the http version to
2.0. But the connection established via the client and the microgateway and
microgateway with the backend would be more efficient and fast due to the
features like header compression, it's full multiplexed nature etc.
Furthermore, we won't be using the server push feature in the microgateway
since there's no much use cases of it with the microgateway.
Thank you
Best Regards,
*Varuni Punchihewa*
Intern - Software Engineering | *WSO2*
*Tel:* +94 71 699 5861
<http://wso2.com/signature>
On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda
wrote:
> Can you please explain how are we planning to go ahead with this feature?
> Even now with ballerina we can create http2 client endpoint or server
> endpoint with http2 follows.
> If we do same now how will it work with existing filters?
>
> endpoint http:Listener testEP {
> port: 9095,
> httpVersion: "2.0"
> };
>
> Thanks,
> sanjeewa.
>
> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa wrote:
>
>> Hi all!
>> Please find my project description and the design as below.
>>
>> *Project description*
>>
>> The WSO2 API Microgateway currently supports only http and https as the
>> incoming and outgoing transport protocols. This project is for enabling it
>> to support HTTP2 for both incoming and outgoing message flows. We need to
>> evaluate the use of OAuth2.0, and rate limiting capabilities on the current
>> Microgateway and see how this impacts the move to HTTP2.
>>
>> *Solution Design*
>>
>>- Supporting the messages received by the microgateway from the
>>clients, by both HTTP/1.1 and HTTP/2.0 protocols
>>- All the communication that happen between the Microgateway and the
>>Back end service will support HTTP/2.0 (The maximum version supported is
>>set to 2.0. In case if it supports only 1.1, then it will be backward
>>compatible to 1.1 and would not be a problem to communications)
>>
>> Best Regards,
>>
>> *Varuni Punchihewa*
>> Intern - Software Engineering | *WSO2*
>>
>> *Tel:* +94 71 699 5861
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> *Sanjeewa Malalgoda*
> Software Architect | Associate Director, Engineering - WSO2 Inc.
> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
> <http://sanjeewamalalgoda.blogspot.com>, Medium
> <https://medium.com/@sanjeewa190>
>
> GET INTEGRATION AGILE <https://wso2.com/signature>
> Integration Agility for Digitally Driven Business
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Solution Design : Support for HTTP2 on the Microgateway
Hi all! Please find my project description and the design as below. *Project description* The WSO2 API Microgateway currently supports only http and https as the incoming and outgoing transport protocols. This project is for enabling it to support HTTP2 for both incoming and outgoing message flows. We need to evaluate the use of OAuth2.0, and rate limiting capabilities on the current Microgateway and see how this impacts the move to HTTP2. *Solution Design* - Supporting the messages received by the microgateway from the clients, by both HTTP/1.1 and HTTP/2.0 protocols - All the communication that happen between the Microgateway and the Back end service will support HTTP/2.0 (The maximum version supported is set to 2.0. In case if it supports only 1.1, then it will be backward compatible to 1.1 and would not be a problem to communications) Best Regards, *Varuni Punchihewa* Intern - Software Engineering | *WSO2* *Tel:* +94 71 699 5861 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
