Would it not be better to generate a unique file-name? I suppose with three image-converters running (as is the default IIRC), this could go wrong?
I'm using File.createTempFile, from the Javadoc:
Creates a new empty file in the specified directory, using the given prefix and suffix strings to generate its name. If this method returns successfully then it is guaranteed that:
1. The file denoted by the returned abstract pathname did not exist before this method was invoked, and
2. Neither this method nor any of its variants will return the same abstract pathname again in the current invocation of the virtual machine.
+ * @since MMBase-1.8
Since you talked about adding to the 1.7 branch, this should be @since MMBase-1.7.2, isn't it? :-)
Yes, but I wanted to wait for some opinions and the vote before adding it to the 1.7 branch. Then I'll change it.
Jaco
