feat: ✨ Allow saving of compose_data somewhere other than in the session

[Rotomeca]

We are experiencing issues due to saving compose_data in the session when there are a large number of users.
We’ve therefore found a solution by saving compose_data in the cache instead.
We’re submitting this idea to you

[alecpl]

The idea to slim down the session is not new, and it makes sense. But could you explain what problems did you encounter specifically?

Also, I think we should consider just using a separate DB table. Use of redis/memcache for this purpose seems unnecessary.

[Rotomeca]

The idea to slim down the session is not new, and it makes sense. But could you explain what problems did you encounter specifically?

Also, I think we should consider just using a separate DB table. Use of redis/memcache for this purpose seems unnecessary.

Randomly, we have users with "Invalid Compose ID" in the logs, and they are unable to send the email. When I debug, in compose.php, the data is present all the way to the end of the script. But in send.php, the data is no longer there. When we check in Redis, we see that compose_data is null. We don't really know why.

I'm okay with just putting it in a table, I suggested the other options for consistency and to leave a choice and if someone would'nt load the database.