[Cubicweb] Implementing set_message and co with pyramid flash queues

Sylvain Thénault sylvain.thenault at logilab.fr
Tue May 5 15:42:57 CEST 2015


On 25 avril 21:06, Christophe de Vienne wrote:
> Hi again everyone,
> 
> Since removing _cwmsgid can be long and tedious (see my previous
> message), I lowered my ambitions about what would be implemented on top
> of the pyramid system.
> 
> I think I found a balanced solution that keep the _cwmsgid mechanism as
> it is but uses a dedicated pyramid flash queue for storing the message.
> 
> Could someone familiar with this API and its expected behavior(s) have a
> look at my patch ?
> 
>   https://www.cubicweb.org/patch/5298671

sounds good, though one would also need to grasp the pyramid flash queue. For
instance, if concurrent requests are displaying a form, each storing
a msgid in the session, will post of each form in any order retrieve the correct
message?

If that's fine, I guess you're patch is fine.

-- 
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
CubicWeb, the semantic web framework:    http://www.cubicweb.org



More information about the Cubicweb mailing list