On Thu, 10 Jan 2013 13:57:54 +0100 Stephan Beal <sgb...@googlemail.com> wrote:
> On Thu, Jan 10, 2013 at 1:53 PM, Eduardo Morras <emorr...@yahoo.es> wrote: > > > If he tries in shell 1 > > > > fossil open repository > > fossil server > > > > and in shell 2 > > > > fossil clone http://localhost:8080/ copy.fossil > > > > should workaround it, the repository is opened only once > > > > In theory, yes, but the web server forks a child process for each request > and (as i learned via a recent thread in the sqlite list) the db must be > opened by the child processes in order for locking to work properly. If BSD > is not killing the child processes immediately after each request is > finished then the db could be held open during the multiple requests sent > by a clone operation. In theory/speculation. I thought that only in cgi mode it's forked for each request, I have to look that part of fossil code more deeply. I think in server mode fossil could/should/may keep running without exit after each request. It could make easier the xfer code for clone pull and push, so a cookie is not needed to continue the download/upload. > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal --- --- Eduardo Morras <emorr...@yahoo.es> _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
