So, the solution which eventually came on such parameters:
1) Files can be loaded in several stages, i.e., added, removed, added and so on.
2) Preview of files is stored in the browser, no download to submission of the main form to the server in order to prevent the dead download - when people close the form nedosypanija, but podgruzit files.
3) Files loaded on the server submit forms with lots of fields and linkouts with the object.
1) so as to write the owner was too lazy to pull with gichaba
a half-hearted decision, and "after the Assembly of processed a file" (to whom interesting - write to put it somewhere or forco branch). What can this creation out of the box: load the files of pictures and do a preview with the delete button. All files are recorded in a separate array, which in the end push-button(optional immediately upon uploading with screws) Ajax sends it to the server files to generate a custom event when the download is complete. Something else, but other chips are not needed.
2) as a result of turning was added a few properties - the maximum number of files maximum file size maximum size for the whole set and the token. Now it is able to swear on the exceeding of limits and send not only files that are added to the array, but the key-token.
3) On main form was hanged the listener onsubmit which checked filesSended variable, by default set to false, and at the FALS did preventDefault form, Ajax had sent the files and the token on the service, after the download completes, fire the listener for the event of loading, which exhibited filesSended in labor, and again submiter basic form, without preventDefault. It looks like simple form submission with a reboot.
4) On the server the files are accepted into a write path and token, and then triggers the form handler on the server come the rest of the data and take the token from the hidden input. One of them is built the object aydishnik and the token is passed to the object images, the method ->relinkImages($id,$token); Method pulls all the pictures with the given token, change the link field to the desired ID, clears the token and saves the recording. All!
5) as a paranoia session written all tokens issued to the user to download images and data availability of the comer post of the token is checked in the session.
A special thank you for the clever ideas, tips and great knowledge of the topic himself in ZHS "float".