[Cubicweb] Pyramid & Cubicweb sessions/authentication integration

Aurélien Campéas aurelien.campeas at logilab.fr
Mon Jul 7 16:10:28 CEST 2014

On 07/07/2014 15:57, Christophe de Vienne wrote:
> The thread having a lot of leaves, I will summarize my point and target :
> I think the session.DATA of cubicweb needs not to be a repository concept.
> It belong to the "web" layer, or could be say the "application" layer.
> If, in some cases, some chosen datas needs to be made available to
> hooks, having connection-bounded data is enough.
> This would allow, if we switch the web layer of cubicweb to a pyramid
> based one, to use the session API of pyramid, thus make use of the
> numerous backends that implement it.
> As for not mistaking web session data and repo session data, it seems to
> me that repo session data is unnecessary.
> And, to be clear, I am not looking for extreme flexibility. All I want
> is to place the right concept in the right place so that we can make use
> of the pyramid ecosystem, while not having too much web-related things
> in the shell script (ie the repo) api.
> So I definitely includes the "application developer" in my vision.
> I hope it clarifies my goal.

Oh, in other words, it's a cubicweb/pyramid impedance mismatch issue,
isn't it ?

I guess these kind of issues would be quickly settled if we were working
together in the same room for a few hours ... :)


More information about the Cubicweb mailing list