HTTP Parser


(James Lei) #1

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?


(Thiago Holanda) #2

Hi James, the early adopters form Swift Server APIs will be the
stakeholders team or who want to test what the steering team develop.

TH


(Jean-Daniel) #3

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.

···

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?


(Tyler Cloutier) #4

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


(Logan Wright) #5

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


(Paulo Faria) #6

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 <mailto: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 <mailto:swift-server-dev@swift.org>> wrote:
>
>
>> Le 7 nov. 2016 à 16:46, James Lei via swift-server-dev <swift-server-dev@swift.org <mailto: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 <mailto:swift-server-dev@swift.org>
> https://lists.swift.org/mailman/listinfo/swift-server-dev

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org <mailto: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


(Logan Wright) #7

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


(Chris Bailey) #8

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


(Logan Wright) #9

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


(Chris Bailey) #10

Hi Logan:

If its going to be the 21st, we should probably get the URLs set up and
the announcements out today.

Chris

···

From: Logan Wright <logan@qutheory.io>
To: Chris Bailey/UK/IBM@IBMGB
Cc: Paulo Faria <paulo@zewo.io>, swift-server-dev@swift.org
Date: 15/11/2016 16:54
Subject: Re: [swift-server-dev] HTTP Parser

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

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


(Logan Wright) #11

Chris, that sounds great. Let's do the 21st at 1pm (eastern) that seems to
have the most people possible. Let me know if I can help w/ the webex!

- Logan

···

On Fri, Nov 18, 2016 at 12:35 PM Chris Bailey <BAILEYC@uk.ibm.com> wrote:

Hi Logan:

If its going to be the 21st, we should probably get the URLs set up and
the announcements out today.

Chris

From: Logan Wright <logan@qutheory.io>
To: Chris Bailey/UK/IBM@IBMGB
Cc: Paulo Faria <paulo@zewo.io>, swift-server-dev@swift.org
Date: 15/11/2016 16:54
Subject: Re: [swift-server-dev] HTTP Parser

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* > <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* <swift-server-dev@swift.org>>
To: Paulo Faria <*paulo@zewo.io* <paulo@zewo.io>>
Cc: *swift-server-dev@swift.org* <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*
<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* <swift-server-dev@swift.org>
*https://lists.swift.org/mailman/listinfo/swift-server-dev*
<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

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


(Chris Bailey) #12

Ok, I've set up the WebEx - here's the URL:
        
https://meetings.webex.com/collabs/#/meetings/detail?uuid=M8C65H48UFLXGRIS8N2GVWH0DV-1T5J&rnd=78810.922722

If you also create a PR against the work group project on GitHub to create
the meeting agenda, then we can use @swift-server/stakeholders to notify
all of the stakeholders. The following PR did that for the Networking
kick-off:
        https://github.com/swift-server/work-group/pull/40

Thanks,

Chris

···

From: Logan Wright <logan@qutheory.io>
To: Chris Bailey/UK/IBM@IBMGB
Cc: Paulo Faria <paulo@zewo.io>, swift-server-dev@swift.org
Date: 18/11/2016 17:42
Subject: Re: [swift-server-dev] HTTP Parser

Chris, that sounds great. Let's do the 21st at 1pm (eastern) that seems to
have the most people possible. Let me know if I can help w/ the webex!

- Logan

On Fri, Nov 18, 2016 at 12:35 PM Chris Bailey <BAILEYC@uk.ibm.com> wrote:
Hi Logan:

If its going to be the 21st, we should probably get the URLs set up and
the announcements out today.

Chris

From: Logan Wright <logan@qutheory.io>
To: Chris Bailey/UK/IBM@IBMGB
Cc: Paulo Faria <paulo@zewo.io>, swift-server-dev@swift.org
Date: 15/11/2016 16:54
Subject: Re: [swift-server-dev] HTTP Parser

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

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

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