Yes, basically this is a sore point to use LilyPond as web service.
Even for powerful machines, having 10 persons or so using it is
effectively a DoS on the machine. Not to mention one can create
snippets requiring HOURS to render (say, lyrics with Asian
characters). So it is very critical to restrict number of users, as
well as the content to be rendered.
OK, this poses the following questions:
- What reasonable limitation can be established on the input, in
aspect of either quantity or quality? Regarding quality, is safe mode
enough?
- Is there an option to let LilyPond only render the first page of the
output, since this web service would only serve the first page as PNG?
- Would putting requests in a queue help? Are there benchmarks on the
number of acceptable simultaneous requests?
thSoft
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
