Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signal behaviour with transactions #6

Open
bergie opened this issue Jun 1, 2010 · 0 comments
Open

Signal behaviour with transactions #6

bergie opened this issue Jun 1, 2010 · 0 comments
Labels

Comments

@bergie
Copy link
Member

bergie commented Jun 1, 2010

See mailing list thread:

http://www.midgard-project.org/discussion/developer-forum/midgard2-_transactions-and_signals/

In short:

When transaction is active signals must be buffered and only sent on commit (and then accompanied by transaction id), if GDA backend does not support transactions then we still buffer signals but rollback() triggers commit signal (with a flag set to identify that it should have been a rollback).

Some IPC signals will probably need config option for turning them on/off in constrained environments (for example we probably do not want to send IPC signals while inside a transaction on mobile platforms like Maemo), see Trac ticket 720 for an idea for more modular approach.

(copied from http://trac.midgard-project.org/ticket/1585)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant