mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

---
summary: Cache presence from remote users
...

Introduction
============

This module stores a timestamp of the latest presence received from
users contacts so that the client can see who is online faster when they
sign in, and won't have to wait for remote servers to reply.

Configuration
=============

Just enable the module.

    modules_enabled = {
        -- more modules
        "presence_cache";
    }

Advanced configuration
======================

The size of the cache is tuneable:

    presence_cache_size = 99

Compatibility
=============

Requires 0.10 or later