Message139584
| Author |
neologix |
| Recipients |
Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner |
| Date |
2011年07月01日.15:23:46 |
| SpamBayes Score |
0.3268328 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTineJU2aF-4mFv4QJoPK6izocnGECw@mail.gmail.com> |
| In-reply-to |
<1309443393.6.0.626834234358.issue6721@psf.upfronthosting.co.za> |
| Content |
> Well, I ping my view that we should:
>
Could you please detail the following points:
- what would be the API of this atfork() mechanism (with an example of
how it would be used in the library)?
- how do you find the correct order to acquire locks in the parent process?
- what do you do with locks that can be held for arbitrarily long
(e.g. I/O locks)? |
|