CODEWITHSUNDEEP
jsonswiftalamofirechunked-encoding
Levi Roberts
Levi Roberts

Reputation: 1317

Does Alamofire support chunked data response?

It is unclear as to whether Alamofire supports chunked data for large or progressive data sets. This is a much needed feature for my application, otherwise I may have to look into alternative methods.

On the Alamofire Github page, it states Progress Closure & NSProgress but I'm not sure what that entails.

And per the description on Wikipedia on Chunked data transfer.

Senders can begin transmitting dynamically-generated content before knowing the total size of that content.


For clarity's sake, let me explain why I need this.

Basically I have a very large JSON file that is partially cached. The full JSON file is composed up of smaller JSON objects. I am using iojs / nodejs to send the chunked data via res.write() with Express which knows not to send the Content-Length header AND send it as chunked data. I have verified this works via html/js.


Let me know if you would like for me to provide the code to demonstrate this!

Upvotes: 2

Views: 4507

Answers (3)

MatterGoal
MatterGoal

Reputation: 16430

The correct way to handle chunked response in Alamofire is using stream: 

    let req = Alamofire.request("http://localhost:8080")

    req.stream { (data) in
       print(String(data: data, encoding: String.Encoding.utf8) ?? "No data")
    }

Upvotes: 7

cnoon
cnoon

Reputation: 16643

Alamofire definitely supports Transfer-Encoding: chunked data due to the fact that it is already supported by NSURLSession. Here is a quick example of downloading a chunked image from httpwatch.com.

let request = Alamofire.request(.GET, "http://www.httpwatch.com/httpgallery/chunked/chunkedimage.aspx")
request.progress { bytesReceived, totalBytesReceived, totalBytesExpected in
    println("\(bytesReceived) - \(totalBytesReceived) - \(totalBytesExpected)")
}
request.response { request, response, _, error in
    println(request)
    println(response)
    println(error)
}

debugPrintln(request)

Since the content length of the image is not available, the totalBytesExpected will always be reported as -1 since it is unknown. The bytesReceived and totalBytesReceived are reported properly though. It seems to me that chunked downloads are probably not the best candidate for trying to present download progress to the user since it is of an undefined length.

Another possible feature that could be of use is the new stream functionality on a request. It allows you to store each data chunk as it is downloaded.

If these options don't suit all your needs, please file an issue on our Github project with the issues you are running into so we can investigate further.

Upvotes: 1

Tushar
Tushar

Reputation: 3052

Following might help -

https://github.com/Alamofire/Alamofire#downloading-a-file-wprogress

Downloading a File w/Progress

Alamofire.download(.GET, "http://httpbin.org/stream/100", destination: destination)
         .progress { (bytesRead, totalBytesRead, totalBytesExpectedToRead) in
             println(totalBytesRead)
         }
         .response { (request, response, _, error) in
             println(response)
         }

Upvotes: -1

Related Questions