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 <
[email protected]>:

> 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 <[email protected]> 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 <[email protected]>:
>>
>>>
>>>
>>> On Thu, Dec 20, 2018 at 5:10 PM Sanjeewa Malalgoda <[email protected]>
>>> 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 <[email protected]>
>>>> 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 <[email protected]>
>>>>> 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 <[email protected]>
>>>>>> 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
>>>>>>> [email protected]
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Sanjeewa Malalgoda*
>>>>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>>>>> (m) +94 712933253 | (e) [email protected] | (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
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>
>>>>
>>>> --
>>>> *Sanjeewa Malalgoda*
>>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>>> (m) +94 712933253 | (e) [email protected] | (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) [email protected]
>>> [image: Signature.jpg]
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to