I work with a system designed as lots of little cooperating worker
programs, with boss programs that... well, boss the worker programs
around.
Boss and workers all use the same database.
Sometimes it would be convenient to have a boss start a transaction
and then have the workers do their work in
I would say that in certain contexts it would definitely be
sane/preferable to have a "worker" process work in its boss's transaction.
In the traditional bank example:
Open a transfer transaction:
One application goes to take money out of one account.
The second application goes to put money into
On Wed, Sep 06, 2006 at 03:21:04PM -0700, Wayne Conrad wrote:
> I work with a system designed as lots of little cooperating worker
> programs, with boss programs that... well, boss the worker programs
> around.
>
> Boss and workers all use the same database.
> Today, it would once again be conven
On Wed, Sep 06, 2006 at 03:21:04PM -0700, Wayne Conrad wrote:
> Today, it would once again be convenient to have an exec'd program do
> its work in the context of its parent program's transaction. So,
> before I once again decide that I don't actually want to do that, can
> you tell me... is it po
