Skip to main content
added 22 characters in body
Source Link
JackTheKnife
  • 389
  • 2
  • 4
  • 9

I need to generate a large Excel file (something around 50 megs) and send response to another API which will provide it to the front end for a download option.

My question is if it will be better to save generated Excel file and provide a path as a response to the API for the front end (something similar what web mail apps do) or to create a response to the front end API as a byte array instead of path to the file?

I need to generate a large Excel file (something around 50 megs) and send response to another API which will provide it to the front end.

My question is if it will be better to save generated Excel file and provide a path as a response to the API for the front end or to create a response to the front end as a byte array?

I need to generate a large Excel file (something around 50 megs) and send response to another API which will provide it to the front end for a download option.

My question is if it will be better to save generated Excel file and provide a path as a response to the API for the front end (something similar what web mail apps do) or to create a response to the front end API as a byte array instead of path to the file?

Source Link
JackTheKnife
  • 389
  • 2
  • 4
  • 9

Generate large Excel files and response from API

I need to generate a large Excel file (something around 50 megs) and send response to another API which will provide it to the front end.

My question is if it will be better to save generated Excel file and provide a path as a response to the API for the front end or to create a response to the front end as a byte array?