freeradius 3.0.x HOW TO ULANG read/write all list keys/values

[Michal Tomaszewski]

>> In fact I would like to use redis, which is much faster than SQL.
>  If you're caching, use the cache module.  Don't use redis.
>  It's just too hard to glue together the "cache random attributes" with databases.

I've already made all radius accounting using redis as well as connection between different sessions' records belonging to the same user roaming between different devices in the same pool of devices.
The default cache mechanism is not suitable for me as I need to set different expirations on some records depending on session time parameter and other properties of the user as well as  I need to have full control of data stored in redis. What is more - cache module working with redis has been introduced only in FR 3.1.x
Thus I'd like to develop own-controlled redis storage.
The only I need is the ulang syntax to extract reply parameters stored in string back to the reply list.

Could you be so kind to explain how in ulang can I achieve reading data directly to the reply list from string created e.g. using  "%{pairs:reply:[*]}" syntax?
________________________________________ Uwaga: Treść niniejszej wiadomości może być poufna i objęta zakazem jej ujawniania. Jeśli czytelnik tej wiadomości nie jest jej zamierzonym adresatem, pracownikiem lub pośrednikiem upoważnionym do jej przekazania adresatowi, informujemy że wszelkie rozprowadzanie, rozpowszechnianie lub powielanie niniejszej wiadomości jest zabronione. Jeśli otrzymałeś tę wiadomość omyłkowo, proszę bezzwłocznie odesłać ją nadawcy, a samą wiadomość usunąć z komputera. Dziękujemy. ________________________________ Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer. Thank you. ________________________________