db and multiple processes

Hi Alex, is it fine to have two/many *independent* processes using the same database? The processes do not share a common parent process, so I just want to check that there is NOT any important communication going on between parent and child processes (something like synchronization signals/messa

Re: db and multiple processes

Hi Tomas, > is it fine to have two/many *independent* processes using the same > database? Usually not, though I do it in certain cases. On the lowest level, the db consists of independent objects ("external symbols"). When a process accesses such a symbol, it obtains a read-lock on the db, read

Re: db and multiple processes

Hi Alex, > Usually not, though I do it in certain cases. In what cases and how you do it? I want to split my app into two independent processes (process families): an admin part (quite complex, can change a lot and significantly, can stop quite "often" for upgrades etc.) and public part (quite s

Re: db and multiple processes

Hi Tomas, > In what cases and how you do it? At SmApper we had a set of stand-alone shell tools (i.e. with the first line containing '#!bin/picolisp') that were used to do quick scans of some databases and build reports. They simply loaded the "er.l" of those applications, and called 'pool' on th

Re: db and multiple processes

Hi Alex, > The SmApper system also has an application manager, and tens to > hundreds of interconnected database applications on blade clusters. that sounds impressive, what does it actually mean? Just curious, is that all picolisp processes spread over many machines managing many databases all

Re: db and multiple processes

Hi Tomas, > that all picolisp processes spread over many machines managing many > databases all communicating (interconnected, in what sence?) to solve > one (or many "unrelated") business problem? I looked at SmApper > website and it seems quite a secret technology;-) Well, then I cannot tell t

Re: db and multiple processes

On Fri, Nov 28, 2008 at 01:15:46PM +0100, Alexander Burger wrote: > If you go with a common database, I would do it like this: The parent > process only loads "lib/http.l" and a common "er.l", defines a function Another great advantage of this solution is that you don't even have to stop any of th

Re: db and multiple processes

Hi Alex, > What I'd like to know first: Is it necessary here that they both > share a common database, or would it also be conceivable that each > has its own database, and they just exchange information? yes, I managed to "export" data from the admin part (at suitable times) for the 24/7 part so

Re: db and multiple processes

Hi Tomas, > > They exist since picoLisp-2.3.3. Is there no "doc/refE.html#*Ext"? > > I cannot find it even in picoLisp-2.3.3 or the testing version:-( Well, then I'm rather worried. Something must be really wrong with the distribution mechanism ;-) If you look at line 31 of "doc/refE.html" (in

Re: db and multiple processes

Hi Alex, > Well, then I'm rather worried. Something must be really wrong with > the distribution mechanism ;-) found it. I am sorry, something seriously wrong with me:-( Cheers, Tomas -- UNSUBSCRIBE: mailto:[EMAIL PROTECTED]