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

ozone framework should not exit if errors are encountered. #48

Open
pliablepixels opened this issue Jul 12, 2016 · 2 comments
Open

ozone framework should not exit if errors are encountered. #48

pliablepixels opened this issue Jul 12, 2016 · 2 comments
Assignees
@web2wire

Comments

@pliablepixels
Copy link
Contributor

pliablepixels commented Jul 12, 2016 •
edited
Loading

Fatal should be sparingly used and program exits only when its in a really messed up state. Missing RTSP feeds/timeouts etc are not candidates for program exit.
@pliablepixels pliablepixels changed the title Usage of Fatal to be reduced only for really critical issues ozone framework should not exit if errors are encountered. Jul 13, 2016
@pliablepixels
Copy link
Contributor Author

@web2wire - would be good if you could PR one use case - example incorrect RTSP url and I can take a similar style for others.

@pliablepixels
Copy link
Contributor Author

This is done for ozAVInput with a try catch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@web2wire web2wire

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@web2wire @pliablepixels