[swift-server-dev] Another way of designing server side

Tyler Cloutier cloutiertyler at aol.com
Mon Nov 7 02:41:15 CST 2016

> On Nov 7, 2016, at 12:27 AM, Brent Royal-Gordon via swift-server-dev <swift-server-dev at swift.org> wrote:
> A web framework ought to be opinionated and consistent, and thus should have a strong, single-paradigm design. But the working group is not designing a web framework; it's designing the *infrastructure* for web frameworks. Designers should be able to take the output of this group and use it to make a framework that matches their vision of web programmer. One developer might design a traditionally functional framework; another might design a functional reactive one; a third might design a class-based MVC framework; a fourth might design a highly dynamic "convention over configuration" framework; a fifth might be very careful to file all the edges off. All of them should be able to use the networking, security, protocol, etc. primitives this group designs.


The infrastructure needs to be able to support each type of web framework, while still providing Swifty APIs for networking. Handling (or explicitly not handling) asynchrony will be an interesting part of this I think.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-server-dev/attachments/20161107/846bf62c/attachment.html>

More information about the swift-server-dev mailing list