You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Binary data support for fetch and XMLHttpRequest #570
Reacted by Joshua, Satish POKALA, Kumaran, Thyagarajan CHATHURBUJAN, Brad Seefeld, Antoine Bouquet, xavierburzig, Dick Smith, Ryan Pendergast, Vineesh and 1 more
May i know when we all can expect this feature avail?
Issue i have faced and my personal need of this feature!
I need to download the byte array from the server through http post api call. The byte array will be hold different type of attachments files/documents which will sizes around 60 to 100 MB's. Once i download & decompress the byte array to local file system then only i can proceed further in my application.
Still i cannot get any proper solution/idea on this. I got stucked in this step. I got confused with this.
Can you people suggest me anything in this moment !!
Reacted by Caius Citiriga, Moritz A. Vieli, Brad Seefeld, crankshift, Chris Johns, Ryan Pendergast and Basil
Activity
satish-pokala-everteam commentedon Nov 6, 2017
writesync is not working with binary data any update on this ?
kumarandena commentedon Nov 6, 2017
Hey @enchev & @NickIliev Any update on this feature request?
May i know when we all can expect this feature avail?
Issue i have faced and my personal need of this feature!
I need to download the byte array from the server through http post api call. The byte array will be hold different type of attachments files/documents which will sizes around 60 to 100 MB's. Once i download & decompress the byte array to local file system then only i can proceed further in my application.
Still i cannot get any proper solution/idea on this. I got stucked in this step. I got confused with this.
Can you people suggest me anything in this moment !!
caiusCitiriga commentedon Apr 16, 2018
Any news on this?
surdu commentedon Jun 13, 2020
This should have been fixed in #7707