Hi. Have you seen http://user-agent-string.info/ ? Now redirects to paid version at http://udger.com/

spam e-mail ?

From time to time the UAS server disappears. This causes significant delays on page requests waiting for a cache update.

It should be possible to init the Parser class with a flag to prevent a cache update so the front-end based calls will only use cached data and a cron job or similar can repopulate the cache.

This can be somewhat achieved by initing the Parser class with an extremely long updateInterval, but if my cron job fails to update the uasdata file and leaves the updatestatus set to false then the frontend call will still attempt to update the cache.

Thanks for the updates yesterday.

One final request, can you please add a tag for 0.53 so composer can grab the correct version without having to use dev-master.

On line 325 of Parser.ini the download of the cache file can be skipped if the current cache file is up to date. This code does not update the cache.ini so any subsequent request will also attempt to update the cache.

Prior to the return true on line 326, the cache.ini should be updated to reflect the update attempt.

Can you set up autoloading in composer.json?

A successful cache update logs a lastupdatestatus of "1" to the cache.ini file (line 364 of Parser.php).

When loading data the DownloadData routine is triggered if lastupdatestatus is not equal to "0" (line 277 of Parser.php).

This results in DownloadData always being called.

There has already been Issue #1 with autoloading, where the proposed fix was to add this to composer.json:

"autoload": {
    "psr-0": {
        "UAS": "UAS/"
    }
}

However, I think it still does not work the way it is intended by composer. Usually, all you have to do is to include vendor/autoload.php and then using the class (i.e. new \UAS\Parser()) should work automatically. However, if I do that, I will get a 'PHP Fatal error: Class 'UAS\Parser' not found' error.

I forked the repo and changed the "UAS": "UAS/" to "UAS": "" and it seems to work. You can have a look at the commit here: moee@2f4f8ba

The tests seem to run, but I am not sure if backwards compatibility is maintained. If you think it is ok, then I could add a pull request.