[File Upload] Problem in multi server environment

Forge Component
(20)
Published on 8 Aug (2 weeks ago) by Renato Pauleta
20 votes
Published on 8 Aug (2 weeks ago) by Renato Pauleta

Hi,

After some tests in a multi server environment, this plugin seams not to work correctly.


Do you have any suggestion how to fix it?


Thanks,

Renato


Solution

Hello Renato,


Recently we had that same problem, your flow is correct. 

Our approach was to change to the multiple file upload plugin, which already has this situation solved, we already test it, in a multiple Front-end server scenario.


I noticed that we can configure plugin: 

  • chunk size - by making it bigger you can guarantee that it will be sent to server 1, although if the file gets bigger than the chunk you might face the situation above.
  • Send HandlerURL: define your endpoint (REST for example), and make all the logic by your self. Concatenate binary files and so on.

Disclaimer: I never really implemented these approaches, we picked the Multiple file upload


Regards,

Solution

Hi Davide,


We did the same :-).


Probably this plugin should have this limitation in a disclaimer.


Thanks,

Renato


Davide Periquito wrote:

Hello Renato,


Recently we had that same problem, your flow is correct. 

Our approach was to change to the multiple file upload plugin, which already has this situation solved, we already test it, in a multiple Front-end server scenario.


I noticed that we can configure plugin: 

  • chunk size - by making it bigger you can guarantee that it will be sent to server 1, although if the file gets bigger than the chunk you might face the situation above.
  • Send HandlerURL: define your endpoint (REST for example), and make all the logic by your self. Concatenate binary files and so on.

Disclaimer: I never really implemented these approaches, we picked the Multiple file upload


Regards,




Hi Renato and Davide,

Indeed by default the component stores the chunks on each front-end temp folder, creating a limitation in multiple front-end scenarios. This disclaimer was added to the component description as mentioned by Renato.

On top of this, let me share with you that a new version (still under development, as more tests are still required) was published first solving the issue reported in another post, regarding the file path being shared in each request, as well as adding a new demo app showing how to use a different file handler to store the chunks on the Database. This is a configuration of the plugin that allows anyone to create each own file handler to support scenarios where the chunks are store in different locations (DB, shared folder, external document management - dropbox, gdrive, aws S3, etc...).

Feel free to test and share your feedback on this new demo app added to the component.


Thanks!