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.

Sign up for GitHub

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

Jump to bottom

GemShutdown policy needed #20

Open
dalehenrich opened this issue May 27, 2014 · 1 comment
Open

GemShutdown policy needed #20

dalehenrich opened this issue May 27, 2014 · 1 comment

Comments

@dalehenrich
Copy link
Member

See the discussion on corruptObj error in glass mailing list ... when a gem must be shutdown, System logout is the natural approach, but not aplicable for all production situations, if we define a shutdown policy, we can allow the application developer to choose his/her poison whether that be, System logout, or sending a mail message, or something else.
@dalehenrich
Copy link
Member Author

seems to be related to https://github.com/GsDevKit/gsApplicationTools

@dalehenrich dalehenrich mentioned this issue Dec 13, 2014
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dalehenrich