[Cubicweb] running the web frontend and cw backend as 2 separate processes on the same machine

Sylvain Thénault sylvain.thenault at logilab.fr
Fri Jun 11 15:53:57 CEST 2010

On 11 juin 15:45, Aurélien Campeas wrote:
> > Though I'm afraid this won't be doable until we have persistent session
> > (else one instance doesn't know anything about session of the other
> > instance). Also that depends on things you may be doing in your hooks, 
> > telling if you can get multiple instances without problems.
> Actually what I see is the following: all long-running transactions are
> also asynchronous transactions. Like:
> When importing a case (this takes on average several minutes), just
> create the case entity, mark it as "importing", store the excel file
> somewhere in a shared place for later use.
> Then, on a dedicated repo instance, a looping task notices the
> "importing" case, fetches the xl files, and starts the actual import
> process, and possibly updates regularly some progress info about the
> import process.
> Same idea for delete, clone.

I think that could be done without any change to cw, I don't see
any show-stopper to deal with it in our cube.

Sylvain Thénault                               LOGILAB, Paris (France)
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