After fetching the Taylor dependency via CocoaPods or Carthage and running as:

$ xcrun swift -F Rome test.swift
LLVM ERROR: Program used external function '__TMaC6Taylor6Server' which could not be resolved!

Currently researching this issue

This would make asking silly questions easier since one would be asking in a more relaxed environment. It's also neat for discussion where you don't want to create a Github issue to reach out to the community.

Please fix that capitalisation of Xcode in README.md:

Swift 2.0 required. Working with xCode 7.1.

It's a bad first impression if you misspell Xcode...

Installing Taylor framework fails and giving the following error "fatal: repository 'https://github.com/nypisces/Taylor.git/' not found" It seems that taylor github path is wrong...

PodFile ---Start---- platform :osx, '10.9' platform :ios, '8.0' plugin 'cocoapods-rome'

pod 'Taylor'

--End--

pod install Updating local specs repositories

CocoaPods 0.39.0.beta.4 is available. To update use: gem install cocoapods --pre [!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies Downloading dependencies Installing AFNetworking (1.3.4) Installing ISO8601DateFormatterValueTransformer (0.6.1) Installing RKValueTransformers (1.1.2) Installing RestKit (0.25.0) Installing SOCKit (1.1) Installing Taylor (0.1.0)

[!] Error installing Taylor [!] /usr/bin/git clone https://github.com/nypisces/Taylor.git /var/folders/zx/xkz4mnmj58s52gct0mc2hzbh0000gn/T/d20150909-18579-g54bgr --single-branch --depth 1 --branch 0.1.0

Cloning into '/var/folders/zx/xkz4mnmj58s52gct0mc2hzbh0000gn/T/d20150909-18579-g54bgr'... remote: Repository not found. fatal: repository 'https://github.com/nypisces/Taylor.git/' not found

This causes both carthage and cocoapods-rome to throw errors when installing the library (at least, in my experience).

This should also be reflected in the .podspec.

Right now the scheme builds and passes carthage build --no-skip-current with no issues!

Unfortunately I'm having some strange issues with Xcode on my end, so I can't test if it works in an actual app. Definitely needs some testing before merging.

Needs review.

Valid statements:

server.get("/*", ...)

server.get("/*/something", ...)

server.get("/something/*/", ...)

and pretty much anything else involving the wildcard character *.

I've done some testing on my own but I'm not convinced that it's completely bug-free.

I'm new to both Swift coding and Taylor, been trying to get the example program to run and I keep getting:

server.swift:6:2: error: contextual type for closure argument list expects 3 arguments, but 2 were specified
        req, res in

with my code being:

import Taylor

let server = Taylor.Server()

server.get("/") { 
    req, res in
    res.bodyString = "Hello, world!"
    return .Send
}

let port = 3000
do {
    print("Starting server on port: \(port)")
    try server.serveHTTP(port: port, forever: true)
} catch {
    print("Server start failed \(error)")
}

Just wondering what I'm doing wrong here, I can't work out what any missing parameter would be from reading the Taylor source code right now.

I am new in swift, i cloned this project and import into my Xcode, but it can not run, there are two erros shown, any tips can you help me, thanks advance.

Sample code:

server.errorPage(.NotFound) { req, res in
    res.bodyString = "Sorry, but the page you're looking for doesn't seem to exist!"
    return .Send(req, res)
}

In my testing, it still returns a 404 on an incorrect path, but if the last handler is a .Continue, then it doesn't (which seems to be a good thing).

It also fixes #12 since we can just have all middleware return .Continue and still get the expected results.

The current implementation of the SocketServer only supports HTTP requests that are sent in 1 or 2 chunks, with the additional requirement of the "Content-Length" header being fully contained in the first chunk for POST and PUT requests. HTTP requests however can be sent in an arbitrary number of chunks and a server must only process the request, after all headers and the full body was received.

On a fast localhost connection an additional problem occurs: The current implementation checks if the body was contained in the first chunk, if not, it just calls read() on the socket. But in many cases, the body data is not available on the socket yet, which will result in a socket read error 35 (EAGAIN) and the body data is silently dropped.

I issues a pull request that should fix the above issues. There are still some memory leaks when handling massive amounts of requests, those should be addressed separately.

I made handling of incoming requests more robust. Especially for clients that are sending HTTP requests in multiple chunks. The socket is now detecting when HTTP headers are finished and also supports sending HTTP bodies in multiple segments. This should also fix problems with large bodies or connections with small MTUs. This should fix issue #48

The Hello, World example isn't working at all for me.

my code in app delegate, pasted from the docs: `import Cocoa import Taylor

@NSApplicationMain class AppDelegate: NSObject, NSApplicationDelegate {

@IBOutlet weak var window: NSWindow!


func applicationDidFinishLaunching(aNotification: NSNotification) {

    let server = Taylor.Server()

    server.get("/") { req, res in
        res.bodyString = "Hello, world!"
        return .Send
    }

    let port = 3002
    do {
        print("Starting server on port: \(port)")
        try server.serveHTTP(port: port, forever: true)
    } catch {
        print("Server start failed \(error)")
    }
}

`

The error is : Contextual type for closure argument list expects 3 arguments, but 2 were specified. I've tried for quite a while to get the format of the closure correct but to no avail. where can I find a working example so I can start using this?

Hi guys,

I'm just learning Swift at the moment. I'm coming from PHP where I use the framework Laravel a lot and I'm trying to switch to swift because I find the language much more beautiful and because it can be much more performant. And now I found Taylor and I really like it.

Looking at the source-code of Taylor and specifically the way it uses handlers / middleware I felt inspired to mix your way of doing it with Laravel's way of doing it.

What if a handler looked like this:

{
    request, response, next in

        // I can do all kinds of things here, before I continue to the next middleware

        (request, response) = next(request, response)

        // Here I can do things that need to be handled on the way out,
        // after the controller has run so to speak

        return (request, response)
}

IMO, this is a bit cleaner than calling callback(.Continue(request, response)). Now you can choose between "continue" and "send", simply by choosing whether to call next or not.

And another nice thing about this, I read in #12 that you guys wanted a way to make sure if "Continue" was called last, it would be automatically converted to "Send". Well in this case, that is trivial. All you need to do is add a dummy handler at the end that does nothing but return the request and response immediately.

This way of doing it implied that request and response are value types, not classes, but I think one can just as easily use classes. In that case it would look like this:

{
    request, response, next in

        // I can do all kinds of things here, before I continue to the next middleware

        next(request, response)

        // Here I can do things that need to be handled on the way out,
        // after the controller has run so to speak
}

What do you guys think?

It looks like it would be quite trivial aside from the SwiftSockets dependency. Has the team put any thoughts towards doing this? I'd be happy to help contribute some effort.