aleax at mac.com
Thu Mar 22 15:42:23 CET 2007
Steve Holden <steve at holdenweb.com> wrote:
> > a. fork
> > b. do the memory-hogging work in the child process
> > c. meanwhile the parent just waits
> > d. the child sends back to the parent the small results
> > e. the child terminates
> > f. the parent proceeds merrily
> > I learned this architectural-pattern a long, long time ago, around the
> > time when fork first got implemented via copy-on-write pages...
> Yup, it's easier to be pragmatic and find the real solution to your
> problem than it is to try and mould reality to your idea of what the
> solution should be ...
"That's why all progress is due to the unreasonable man", hm?-)
More information about the Python-list