forked from dalehenrich/gsApplicationTools
-
Notifications
You must be signed in to change notification settings - Fork 2
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
GemServer>>doBasicTransaction: must be non-re-entrant #16
Labels
Milestone
Comments
dalehenrich
added a commit
that referenced
this issue
Jan 9, 2015
dalehenrich
added a commit
that referenced
this issue
Jan 9, 2015
…s (allow for server-side debugging in a tODE client) and fix a basic bug in reentry logic ... still no reentrant tests
dalehenrich
added a commit
that referenced
this issue
Jan 10, 2015
dalehenrich
added a commit
that referenced
this issue
Jan 10, 2015
…inTransaction) ... fix it and restore some code erroneously removed and cross fingers
dalehenrich
added a commit
that referenced
this issue
Jan 12, 2015
done |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After a discussion with @rjsargent, I've decided that the conflicting goals of
manual transaction mode
.automatic transaction mode
.cannot be achieved cleanly. The basic problem is that it isn't possible to tell when it is correct to abort/commit when running in
automatic transaction mode
. Of course, I also don't have a strong case fr needing re-entrant GemServer>>doBasicTransaction: calls, so for now they will be non-re-entrant.The text was updated successfully, but these errors were encountered: