Siofu file uploader analysis

Thre are multiple control parameters that can be used for file upload especially the chunk sizes 

Based on it, the WebSocket will be configured to send that many size in each packet. 

The chunk size really only tells about the 

42["siofu_chunk",{"id":0}] 26

05:47:08.264

451-["siofu_progress",{"id":0,"size":11242812,"start":10240000,"end":11242812,"content":{"_placeholder":true,"num":0},"base64":false}] 134

05:47:08.268

Binary Message 1.0 MB

05:47:08.275

42["siofu_done",{"id":0}] 25

05:47:08.282

42["siofu_chunk",{"id":0}] 26

05:47:09.900

42["siofu_complete",{"id":0,"success":true,"detail":{}}] 56

05:47:09.901

2 1

05:47:14.785

3 1

05:47:15.084

2 1

05:47:40.087

3 1

05:47:40.511

2 1

05:48:05.514

3 1

05:48:05.812

2 1

05:48:30.817

3 1

05:48:31.302

2 1

05:48:56.304

3 1

05:48:56.700

2 1

05:49:21.704

3 1

05:49:22.004

2 1

05:49:47.006

3 1

05:49:47.333

Data: 2probe, Length: 6, Time: 05:46:50.713

1

2probe

Trying with different chunk sizes, below are the results 

Whatever chunk size that is set before starting the upload, that many bytes of data is sent as WebSocket messages. 

The main drawback of the nam is it does not allow the chunk size to be altered after the upload operation starts.

This restricts us to change the sizes in middle of transfer. Also, the whole concept is based on file storing

This is not helping much as well as the size is constant. 

We need to find some alternative for this. 

References: 

https://www.npmjs.com/package/socketio-file-upload#progress-1