I can understand the PNG from SVG conversion might require temporary file storage to perform. But couldn't SVG generation be directly output as REST/HTTP response (with the appropriate content type) to the client?
Or did you also design it this way in case the SVG chart generation takes a while based on the posted dataset? For me, I would prefer a one step process (where possible) to post and get back results rather than make a render request then check back later to fetch the result, unless I have a very large dataset to process.
Also, it looks like you generate dynamic filenames by default using the system date/time but are you saving to system's temp file location? That would be best in terms of temp file management.
I can understand the PNG from SVG conversion might require temporary file storage to perform. But couldn't SVG generation be directly output as REST/HTTP response (with the appropriate content type) to the client?
Or did you also design it this way in case the SVG chart generation takes a while based on the posted dataset? For me, I would prefer a one step process (where possible) to post and get back results rather than make a render request then check back later to fetch the result, unless I have a very large dataset to process.
Also, it looks like you generate dynamic filenames by default using the system date/time but are you saving to system's temp file location? That would be best in terms of temp file management.