Home IOS Development Hummingbird routing and requests – The.Swift.Dev.

Hummingbird routing and requests – The.Swift.Dev.

0
Hummingbird routing and requests – The.Swift.Dev.

[ad_1]

Routing on the server facet means the server goes to ship a response based mostly on the URL path that the shopper known as when firing up the HTTP request. In fact the server can verify extra parameters and headers to construct the ultimate response, however after we discuss routing typically, we often confer with the trail elements. Hummingbird makes use of a trie-based router, which is a quick and environment friendly manner of wanting up routes. It is fairly easy to answer HTTP request utilizing the built-in router, you possibly can merely add your primary route handlers like this:

 
router.on("foo", methodology: .HEAD) { _ -> HTTPResponseStatus in .okay }
router.on("foo", methodology: .GET) { _ -> HTTPResponseStatus in .okay }
router.on("foo", methodology: .POST) { _ -> HTTPResponseStatus in .okay }
router.on("foo", methodology: .PUT) { _ -> HTTPResponseStatus in .okay }
router.on("foo", methodology: .PATCH) { _ -> HTTPResponseStatus in .okay }
router.on("foo", methodology: .DELETE) { _ -> HTTPResponseStatus in .okay }


router.head("foo") { _ -> HTTPResponseStatus in .okay }
router.get("foo") { _ -> HTTPResponseStatus in .okay }
router.put("foo") { _ -> HTTPResponseStatus in .okay }
router.put up("foo") { _ -> HTTPResponseStatus in .okay }
router.patch("foo") { _ -> HTTPResponseStatus in .okay }
router.delete("foo") { _ -> HTTPResponseStatus in .okay }

In Hummingbird it is usually doable to register use a operate as a substitute of a block. Handler features could be async and throwing too, so you possibly can mark the blocks with these key phrases or use asynchronous Swift features when registering route handlers. In the event you do not present the primary parameter, the trail as a string, the route handler goes to be hooked up to the bottom group. 👍

You too can prefix a path part with a colon, it will flip that part right into a dynamic route parameter. The parameter goes to be named after the trail part, by merely dropping the colon prefix. You may entry parameters inside your route handler via the req.parameters property. Additionally it is doable to register a number of elements utilizing a / character.

public extension HBApplication {
    
    func configure() throws {

        router.get { _ async throws in "Hey, world!" }

        router.get("hi there/:identify") { req throws in
            guard let identify = req.parameters.get("identify") else {
                throw HBHTTPError(
                    .badRequest,
                    message: "Invalid identify parameter."
                )
            }
            return "Hey, (identify)!"
        }

        let group = router.group("todos")
        group.get(use: record)
        group.put up(use: create)
        
        let idGroup = group.group(":todoId")
        idGroup.head(use: verify)
        idGroup.get(use: fetch)
        idGroup.put(use: replace)
        idGroup.patch(use: patch)
        idGroup.delete(use: delete)

        
        router.group("todos")
            .get(use: record)
            .put up(use: create)
            .group(":todoId")
                .head(use: verify)
                .get(use: fetch)
                .put(use: replace)
                .patch(use: patch)
                .delete(use: delete)

    }

    func record(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func verify(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func fetch(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func create(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func replace(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func patch(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
    func delete(_ req: HBRequest) async throws -> HTTPResponseStatus { .okay }
}

It’s doable to make use of a wildcard character () when detecting path elements and the recursive model (*) to catch every part. Additionally you should use the ${identify} syntax to catch a named request parameter even with a prefix or suffix, however you possibly can’t insert this in the midst of a path part. (e.g. “prefix-${identify}.jpg” will not work, however “${identify}.jpg” is simply nice) 💡

import Hummingbird
import HummingbirdFoundation

extension HBApplication {

    func configure(_ args: AppArguments) throws {

        router.get("foo-${identify}", use: catchPrefix)
        router.get("${identify}.jpg", use: catchSuffix)
        
        router.get("*", use: catchOne)
        router.get("*/*", use: catchTwo)

        router.get("**", use: catchAll)
        
    }
    
    
    func catchOne(_ req: HBRequest) async throws -> String {
        "one"
    }

    
    func catchTwo(_ req: HBRequest) async throws -> String {
        "two"
    }
    
    
    func catchAll(_ req: HBRequest) async throws -> String {
        "all: " + req.parameters.getCatchAll().joined(separator: ", ")
    }
    
    
    func catchPrefix(_ req: HBRequest) async throws -> String {
        "prefix: " + (req.parameters.get("identify") ?? "n/a")
    }
    
    
    func catchSuffix(_ req: HBRequest) async throws -> String {
        "suffix: " + (req.parameters.get("identify") ?? "n/a")
    }
}

Additionally it is doable to edit the auto-generated response in the event you specify the .editResponse possibility.

router.get("foo", choices: .editResponse) { req -> String in
    req.response.standing = .okay
    req.response.headers.replaceOrAdd(
        identify: "Content material-Kind", 
        worth: "software/json"
    )
    return #"{"foo": "bar"}"#
}

Hummingbird help for physique streaming is wonderful, you possibly can stream a HTTP request physique through the use of the .streamBody possibility. The physique stream has a sequence property, which you should use to iterate via the incoming ByteBuffer chunks when dealing with the request. 🔄

func configure() throws { 
    router.put up("foo", choices: .streamBody) { req async throws -> String in
        guard
            let rawLength = req.headers["Content-Length"].first,
            let size = Int(rawLength),
            let stream = req.physique.stream
        else {
            throw HBHTTPError(
                .badRequest,
                message: "Lacking or invalid physique stream."
            )
        }
        var depend: Int = 0
        for strive await chunk in stream.sequence {
            depend += chunk.readableBytes
        }
        return String("(size) / (depend)")
    }
}


let app = HBApplication(
    configuration: .init(
        handle: .hostname(hostname, port: port),
        serverName: "Hummingbird",
        maxUploadSize: 1 * 1024 * 1024 * 1024 
    )
)

As you possibly can see you possibly can simply entry all of the incoming headers through the req.headers container, you need to be aware that this methodology will return header values in a case-insensitive manner. If you wish to stream bigger information, you additionally must set a customized maxUploadSize utilizing the configuration object when initializing the HBApplication occasion.

curl -X POST http://localhost:8080/foo 
    -H "Content material-Size: 3" 
    --data-raw 'foo'

curl -X POST http://localhost:8080/foo 
    -H "content-Size: 5242880" 
    -T ~/take a look at

You may check out streaming with a easy cURL script, be happy to experiment with these.

One other factor I would like to indicate you is how one can entry question parameters and different properties utilizing the request object. Right here is an all-in-one instance, which you should use as a cheatsheet… 😉


router.get("bar") { req async throws -> String in
            
    struct Foo: Codable {
        var a: String
    }

    print(req.methodology)
    print(req.headers)
    print(req.headers["accept"])
    print(req.uri.queryParameters.get("q") ?? "n/a")
    print(req.uri.queryParameters.get("key", as: Int.self) ?? 0)

    if let buffer = req.physique.buffer {
        let foo = strive? JSONDecoder().decode(Foo.self, from: buffer)
        print(foo ?? "n/a")
    }
    return "Hey, world!"
}

Anyway, there may be one extra tremendous cool function in Hummingbird that I would like to indicate you. It’s doable to outline a route handler, this manner you possibly can encapsulate every part right into a single object. There may be an async model of the route handler protocol, in the event you do not want async, you possibly can merely drop the key phrase each from the protocol identify & the tactic. I like this method loads. 😍

struct MyRouteHandler: HBAsyncRouteHandler {

    struct Enter: Decodable {
        let foo: String
    }

    struct Output: HBResponseEncodable {
        let id: String
        let foo: String
    }
    
    let enter: Enter

    init(from request: HBRequest) throws {
        self.enter = strive request.decode(as: Enter.self)
    }

    func deal with(request: HBRequest) async throws -> Output {
        .init(
            id: "id-1",
            foo: enter.foo
        )
    }
}

The request.decode methodology makes use of the built-in decoder, which it’s a must to explicitly set for the applying, since we’ll talk utilizing JSON information, we will use the JSON encoder / decoder from Basis to routinely rework the information.

To be able to make use of the customized route handler, you possibly can merely register the thing sort.

import Hummingbird
import HummingbirdFoundation

public extension HBApplication {

    func configure() throws {
        
        encoder = JSONEncoder()
        decoder = JSONDecoder()
                
        
        router.put up("foo", use: MyRouteHandler.self)
    }
}

You may learn extra about how the encoding and decoding works in Hummingbird, however possibly that matter deserves its personal weblog put up. In case you have questions or recommendations, be happy to contact me. 🙈

[ad_2]

LEAVE A REPLY

Please enter your comment!
Please enter your name here