Hi, could you please add Reachability as a dependency and/ or write this in the documentation? I added pod 'ReachabilitySwift', '~> 2.1' to my podfile and needed to update your example to the code below:

func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {

        setupCaching()

        return true
    }

    private func setupCaching(){

        do{
            let reach = try Reachability.reachabilityForInternetConnection()
            try reach.startNotifier()
            let kB = 1024
            let MB = 1024 * kB
            let GB = 1024 * MB
            let isOfflineHandler: (() -> Bool) = {
                let isOffline = reach.currentReachabilityStatus == Reachability.NetworkStatus.NotReachable
                return isOffline
            }
            let urlCache = Mattress.URLCache(memoryCapacity: 20 * MB, diskCapacity: 20 * MB, diskPath: nil,
                mattressDiskCapacity: 1 * GB, mattressDiskPath: nil, mattressSearchPathDirectory: .DocumentDirectory,
                isOfflineHandler: isOfflineHandler)

            NSURLCache.setSharedURLCache(urlCache)
        }
        catch let err as NSError {
            print("Error with caching: " + err.localizedDescription)
        }
    }

I have recognized that a page often ends loading with a different state. I printing the line let state = webView.stringByEvaluatingJavaScriptFromString("document.readyState") to the console. Sometimes it finishes with "interactive" and sometimes with "completed" when loading the same url. Should the caching process then be repeated?

I tried to cache different pages consequently by calling.

cachePage(SiteA)
cachePage(SiteB)
cachePage(SiteC)

Is it possible that I have to wait until the former caching process has been completed? What I'm trying to achieve is that my apps caches certain pages after initialization to present them as fast as possible when the user visits them.

Another question: Does the caching mechanism needs an instance of a webView in my class or can it cache independently, so that I can put cachePage in it's own model class?

    func cachePage(url: NSURL) {
        log.info("Caching page \(url.absoluteString)")
        if let cache = NSURLCache.sharedURLCache() as? Mattress.URLCache
        {
            cache.diskCacheURL(url, loadedHandler: { (webView) -> (Bool) in
                    let state = webView.stringByEvaluatingJavaScriptFromString("document.readyState")
                    log.verbose("state: \(state)")
                    return state == "complete"
                }, completeHandler: { () -> Void in
                    log.info("Finished caching \(url.absoluteString)")
                }, failureHandler: { (error) -> Void in
                    log.error("Error caching: \(error.localizedDescription)")
            })
        }
    }

Hi - i currently have a big Objective C Project that will not be migrated to Swift. It has been migrated to iOS9 as minimum deployment target.

Now I imported Mattress via cocoapods and and added the use_frameworks! tag. This causes problems with other imported libraries.

Have you planned to implement support for Objective C that is compatible to other library? Another point is that I get a warning regarding deprecation of NSURLConnection in your lib with iOS9.

I found that this is a working solution for #40 not sure how the merging process will affect the current pod, but after testing this fork out it seemed to work fine in Swift 3.

@lordkev

I keep seeing this issue show up where in offline mode it just immediately loads a white page. I think it's failing and then saving that failure for later so we just keep getting it.

@dmauro @sharpfive

Let me know if you see anything missing or if you think something's overkill. I leaned on the side of thoroughness even if some things were likely obvious anyway.

I'm creating a conference app with an integration of some websites for venue, sponsors etc. This pages do not change quite often and it would be great to ship them cached with the app store build.

Some users start the app at the conference center for the first time where wifi conditions are sometimes very poor. Instead of showing a blank page the users should see at least "something".

It would be great if mattress could support this. What I currently would do is caching the websites within the simulator, cache the contents of the required pages and zip the mattress folder afterwards to ship it with the app (Currently there is a bug, see https://github.com/buzzfeed/mattress/issues/33).

Is there something that can be solved by mattress to improve this process? For example that mattress could create the zip-file and present a mail dialog to bring the file to the devs machine? Or to update the cache automatically before creating the app store build? Will the cache be working on other devices?

Hi, after installation via cocoa pods this line let urlCache = Mattress.URLCache(memoryCapacity: 20 * MB, diskCapacity: 20 * MB, diskPath: nil, mattressDiskCapacity: 1 * GB, mattressDiskPath: nil, mattressSearchPathDirectory: .DocumentDirectory, isOfflineHandler: isOfflineHandler)

shows an error Use of unresolved identifier 'Mattress'

Based this on the following SO answers. It uses a dummy framework to import CommonCrypto so that the end user of Mattress doesn't have to add the module map to their own project.

http://stackoverflow.com/questions/24123518/how-to-use-cc-md5-method-in-swift-language

http://stackoverflow.com/questions/25248598/importing-commoncrypto-in-a-swift-framework

I need to save multiple pages as user navigate through them, in example and in wiki you have used only 1 url should i use different database to store requested pages?

Looks like there was a trailing slash missing that was causing all files to be stored in the root Documents directory.

Per issue https://github.com/buzzfeed/mattress/issues/33.

@dmauro

When including Mattress via CocoaPods and manually specifying the SWIFT_VERSION to 2.3, I get a compilation error with DiskCache.diskPath() (line 457):

if !NSFileManager.defaultManager().fileExistsAtPath(fileURL.absoluteString, isDirectory: &isDir) {
...
}

The issue stems from the fact that NSFileManager.fileExistsAtPath(...) accepts a non-optional string, so fileURL.absoluteString has to be unwrapped.

I pushed a fix to my own fork and raised a PR - just not too sure if my solution is the most ideal given the rest of the context of DiskCache. Let me know what you think 👍

Added the absolute file path as a separate variable in the let expression so its value can be safely unwrapped and used within NSFileManager.fileExistsAtPath(...) (in order for Mattress to compile properly in Swift 2.3).

It shouldn't affect functionality, but the key used to store our current cache size is labeled as "maxCacheSize", which it is not. The maxCacheSize gets passed in on initialization each time. We should rename that, and while we're at it, go ahead and capitalize those DictionaryKey constants for style.