First of all, congratulations on the 2024R1 release!
I noticed the improvement in memory clean-up after a download: takes about a minute VS much more in previous versions.
But as things still hold, when downloading a file, the entirety of its contents are loaded into memory. For small files it goes unnoticed, for bigger files, it really shows.
I’ve been thinking…would it be a huge refactor in that part of the framework if the download was somewhat chunked and didn’t require all that memory when in progress?
I have to say I tried implementing something like that in this -unrelated to Web2- project, but blew up in my face for reasons I have no way of investigating.
Xojo engineers: Would it be something you could look into?
Xojo users: Would you consider this a meaningful enhancement?
Thanks!
1 post - 1 participant