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

GemServer>>doBasicTransaction: must be non-re-entrant #16

Closed
dalehenrich opened this issue Jan 9, 2015 · 1 comment
Closed

GemServer>>doBasicTransaction: must be non-re-entrant #16

dalehenrich opened this issue Jan 9, 2015 · 1 comment
Milestone

Comments

@dalehenrich
Copy link
Member

After a discussion with @rjsargent, I've decided that the conflicting goals of

  1. running production applications in manual transaction mode.
  2. allowing folks to debug gem servers in automatic transaction mode.
  3. allowing GemServer>>doBasicTransaction: to be re-entrant.

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.

@dalehenrich dalehenrich added this to the 1.0.2 milestone 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 9, 2015
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
Copy link
Member Author

done

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

No branches or pull requests

1 participant