Heterogeneity interpreter integration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 14: | Line 14: | ||
** First interpreter timeout/crash: e.g. First interpreter (.PHP) is timeout but second interpreter (.PY) is still running. | ** First interpreter timeout/crash: e.g. First interpreter (.PHP) is timeout but second interpreter (.PY) is still running. | ||
** Second interpreter timeout/crash | ** Second interpreter timeout/crash | ||
** Process management: Monitor and recycle the process | |||
* System level | * System level | ||
Revision as of 10:29, 17 April 2018
Considerations of multi-languages Interpreter integration
Input / Output
- ill-formed input and output
Unexpected conditions / errors
- Entry point
- Interpreter level
- First interpreter timeout/crash: e.g. First interpreter (.PHP) is timeout but second interpreter (.PY) is still running.
- Second interpreter timeout/crash
- Process management: Monitor and recycle the process
- System level
- e.g. memory error caused by second interpreter
- API level
References
- ↑ Browser Timeouts - Stack Overflow
- ↑ Command prompt (Cmd. exe) command-line string limitation when error message 'The command line is too long.' met on windows.
- ↑ mac osx - What is the maximum length of a command line in Mac OS X? - Server Fault
Related articles
- How to properly call Python 3 script from PHP? - Stack Overflow
- Passing value from PHP script to Python script - Stack Overflow
- Integrating PHP and R | R-bloggers [Last visited: 2017-12-18]
- PHP: set_time_limit - Manual
- Run Python script from php, save process pid, and don't wait it to finish - Stack Overflow un-verified