<tt><font size=2>> I think the right solution in general is to use
C quite aggressively at first, but wall it off behind Swift facades. Later,
we can revisit our C dependencies and replace them with Swift as we feel
it's appropriate. Ideally, we'd use protocols here so the replacement is
as simple as possible.</font></tt>
<br>
<br><font size=2 face="sans-serif">+1</font>
<br><font size=2 face="sans-serif"><br>
Chris</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Brent Royal-Gordon
via swift-server-dev <swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Logan Wright <logan@qutheory.io>,
Logan Wright via swift-server-dev <swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">04/11/2016 20:34</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [swift-server-dev]
HTTP Parser</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">swift-server-dev-bounces@swift.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>> On Nov 4, 2016, at 12:18 PM, Logan Wright via
swift-server-dev <swift-server-dev@swift.org> wrote:<br>
> <br>
> Helge, if I had my way, we wouldn't touch C in any way whatsoever
for any of the server side libraries except as an absolute last resort,
but this life is full of compromise, and I'm trying to be amicable to come
up with solutions that we can agree on.<br>
> <br>
> For HTTP2 as well, I'd like plans to eventually move to pure swift
native implementations rethought for the language. <br>
<br>
I think the right solution in general is to use C quite aggressively at
first, but wall it off behind Swift facades. Later, we can revisit our
C dependencies and replace them with Swift as we feel it's appropriate.
Ideally, we'd use protocols here so the replacement is as simple as possible.<br>
<br>
Here's my question: Can we have our HTTP parser use Foundation's existing
`URLRequest` and `HTTPURLResponse` types as Swift-facing outputs and inputs?
Or are these types too-tightly designed for an HTTP client's needs,
and we need different types for an HTTP server? Or are there minor modifications
the Foundation team is willing to make in Apple Foundation to extend them
for our use case? If we *can* use these types on both client and server,
I think that would be ideal—it would allow people to reuse their knowledge
and potentially a little bit of code.<br>
<br>
-- <br>
Brent Royal-Gordon<br>
Architechies<br>
<br>
_______________________________________________<br>
swift-server-dev mailing list<br>
swift-server-dev@swift.org<br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-server-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>