HTTP Parser


(Wayne N) #1

Tyler Cloutier,

Proposing Node.js HTTP in C would need some benchmark for a comparison
which I assume it would be slower than native Node.js and Perfect using
HTTP in C.

https://medium.com/@rymcol/linux-ubuntu-benchmarks-for-server-side-swift-vs-node-js-db52b9f8270b#.hori7khr1

···

On Wed, Nov 16, 2016 at 12:54 AM, Logan Wright via swift-server-dev < swift-server-dev@swift.org> wrote:

Chris,

That sounds perfect, webex has been a great format so far. Right now it's
looking like 12 eastern time on the 21st or the 23rd.

- Logan

On Tue, Nov 15, 2016 at 9:32 AM Chris Bailey <BAILEYC@uk.ibm.com> wrote:

Thanks for setting this up. I've filled out the Doodle Poll - do you
need/want me to set up a Webex once we've determined the day/time?

Chris

From: Logan Wright via swift-server-dev <
swift-server-dev@swift.org>
To: Paulo Faria <paulo@zewo.io>
Cc: swift-server-dev@swift.org
Date: 11/11/2016 03:07
Subject: Re: [swift-server-dev] HTTP Parser
Sent by: swift-server-dev-bounces@swift.org
------------------------------

Good catch Paulo, fixed, make sure to double check your selections in
case it moved any of them on you.

On Thu, Nov 10, 2016 at 10:03 PM Paulo Faria <*paulo@zewo.io* >> <paulo@zewo.io>> wrote:
I think on Tue 22 the first choice shouldn’t be there? For my timezone it
says 2AM and right next to it there’s a 2PM.

On Nov 11, 2016, at 12:57 AM, Logan Wright via swift-server-dev < >> *swift-server-dev@swift.org* <swift-server-dev@swift.org>> wrote:

Hey everyone, I think it's about time we do some of the http sub-team
kickoff. We can discuss some of the topics in here and more generally start
breaking off.

Here's the doodle for interested. We're shooting for the week of the
21st. We'll also collect minutes for those who can't make it.

*http://doodle.com/poll/e2tffhkaergtd72p*
<http://doodle.com/poll/e2tffhkaergtd72p>

- Logan

On Thu, Nov 10, 2016 at 2:48 AM Tyler Cloutier via swift-server-dev < >> *swift-server-dev@swift.org* <swift-server-dev@swift.org>> wrote:
Additionally, we are proposing using the Node.js, C language, HTTP parser
which has been tested in thousands upon thousands of currently deployed
applications so the likelihood of errors would be much lower than for a
home grown solution.

That being said I do appreciate the desire to be inclusive of developers
who might not be familiar with C. Not to mention the benefits of safety
provided by Swift. I just think in this case since the proposed parser is
so well tested and widely use, it would be the safer option to choose that.

Tyler

> On Nov 8, 2016, at 11:26 PM, Jean-Daniel via swift-server-dev < >> *swift-server-dev@swift.org* <swift-server-dev@swift.org>> wrote:
>
>
>> Le 7 nov. 2016 à 16:46, James Lei via swift-server-dev < >> *swift-server-dev@swift.org* <swift-server-dev@swift.org>> a écrit :
>>
>> if HTTP Parser in C is use along with Swift, it may be difficult for
the Startups and Enterprise to adopt as an early adopters if something will
break, it would be difficult for the developers to debug if it's cause by C
or Swift.
>>
>> I favour writing in Swift from scratch to encourage software engineers
and the like to participate on the same languages from .Net, Java, Node.js,
Go, Rust community, etc
>>
>> Who will be our early adopters?
>
> If the primary users are the frameworks authors, I’m pretty sure the
final users won't care if the low level stuff are C wrappers or a pure
swift as long as it work out of the box and they can deploy and use the
framework easily.
>
>
>
> _______________________________________________
> swift-server-dev mailing list
> *swift-server-dev@swift.org* <swift-server-dev@swift.org>
> *https://lists.swift.org/mailman/listinfo/swift-server-dev*
<https://lists.swift.org/mailman/listinfo/swift-server-dev>

_______________________________________________
swift-server-dev mailing list
*swift-server-dev@swift.org* <swift-server-dev@swift.org>
*https://lists.swift.org/mailman/listinfo/swift-server-dev*
<https://lists.swift.org/mailman/listinfo/swift-server-dev>
_______________________________________________
swift-server-dev mailing list
*swift-server-dev@swift.org* <swift-server-dev@swift.org>
*https://lists.swift.org/mailman/listinfo/swift-server-dev*
<https://lists.swift.org/mailman/listinfo/swift-server-dev>
_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev


(Chris Bailey) #2

Both Perfect and Node.js use the same C HTTP parser that's being referred
to.

Chris

···

From: Wayne N via swift-server-dev <swift-server-dev@swift.org>
To: swift-server-dev@swift.org
Date: 17/11/2016 16:56
Subject: Re: [swift-server-dev] HTTP Parser
Sent by: swift-server-dev-bounces@swift.org

Tyler Cloutier,

Proposing Node.js HTTP in C would need some benchmark for a comparison
which I assume it would be slower than native Node.js and Perfect using
HTTP in C.

https://medium.com/@rymcol/linux-ubuntu-benchmarks-for-server-side-swift-vs-node-js-db52b9f8270b#.hori7khr1

On Wed, Nov 16, 2016 at 12:54 AM, Logan Wright via swift-server-dev < swift-server-dev@swift.org> wrote:
Chris,

That sounds perfect, webex has been a great format so far. Right now it's
looking like 12 eastern time on the 21st or the 23rd.

- Logan

On Tue, Nov 15, 2016 at 9:32 AM Chris Bailey <BAILEYC@uk.ibm.com> wrote:
Thanks for setting this up. I've filled out the Doodle Poll - do you
need/want me to set up a Webex once we've determined the day/time?

Chris

From: Logan Wright via swift-server-dev <swift-server-dev@swift.org

To: Paulo Faria <paulo@zewo.io>
Cc: swift-server-dev@swift.org
Date: 11/11/2016 03:07
Subject: Re: [swift-server-dev] HTTP Parser
Sent by: swift-server-dev-bounces@swift.org

Good catch Paulo, fixed, make sure to double check your selections in case
it moved any of them on you.

On Thu, Nov 10, 2016 at 10:03 PM Paulo Faria <paulo@zewo.io> wrote:
I think on Tue 22 the first choice shouldn’t be there? For my timezone it
says 2AM and right next to it there’s a 2PM.

On Nov 11, 2016, at 12:57 AM, Logan Wright via swift-server-dev < swift-server-dev@swift.org> wrote:

Hey everyone, I think it's about time we do some of the http sub-team
kickoff. We can discuss some of the topics in here and more generally
start breaking off.

Here's the doodle for interested. We're shooting for the week of the 21st.
We'll also collect minutes for those who can't make it.

http://doodle.com/poll/e2tffhkaergtd72p

- Logan

On Thu, Nov 10, 2016 at 2:48 AM Tyler Cloutier via swift-server-dev < swift-server-dev@swift.org> wrote:
Additionally, we are proposing using the Node.js, C language, HTTP parser
which has been tested in thousands upon thousands of currently deployed
applications so the likelihood of errors would be much lower than for a
home grown solution.

That being said I do appreciate the desire to be inclusive of developers
who might not be familiar with C. Not to mention the benefits of safety
provided by Swift. I just think in this case since the proposed parser is
so well tested and widely use, it would be the safer option to choose
that.

Tyler

On Nov 8, 2016, at 11:26 PM, Jean-Daniel via swift-server-dev < swift-server-dev@swift.org> wrote:

Le 7 nov. 2016 à 16:46, James Lei via swift-server-dev < swift-server-dev@swift.org> a écrit :

if HTTP Parser in C is use along with Swift, it may be difficult for

the Startups and Enterprise to adopt as an early adopters if something
will break, it would be difficult for the developers to debug if it's
cause by C or Swift.

I favour writing in Swift from scratch to encourage software engineers

and the like to participate on the same languages from .Net, Java,
Node.js, Go, Rust community, etc

Who will be our early adopters?

If the primary users are the frameworks authors, I’m pretty sure the

final users won't care if the low level stuff are C wrappers or a pure
swift as long as it work out of the box and they can deploy and use the
framework easily.

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev
_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev
_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev
_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU