Jason Davies wrote: > > Robert Wittams wrote: > > >>The temporary location is a slight issue. My current thinking is : >>a temporary location is a directory. It contains two subdirectories, eg >>0 and 1. >>We first use the 0 directory. Then after n minutes, we use the 1 >>directory. After another n minutes, we use the 0 directory again, >>deleting its current contents. This means that any temporary file will >>live for at least n minutes and at most 2n minutes, (as long as requests >>are still being made). >> >>Then, on final save, the file is moved to a more permanent storage area. >>There could be a global temporary area and timeout value, overridable on >>individual file fields. > > > Just an idea: could the file be temporarily stored in the session > instead? At least then it won't be sent "over the wire" multiple > times. Storing it in the session avoids having to introduce yet > another setting variable. However, this would make FileField dependent > on the sessions stuff, which may not be desirable.
I can't really see this as preferable to a setting : * The manipulator has no access to the session, request, etc * The session is pickled into the database, afaik. Is this really sensible with eg a 10 meg file?
