Making "read from file" less blocky.
alex at tweedly.net
Sun Aug 4 13:20:50 EDT 2019
Oh, that's a bit worrying .... I'm just starting a project that will use
httpd, and it might in the medium term need to receive large data sets.
But for now, similar to this case of yours for "serving" files, it only
needs to send large data sets, and I have tested that pretty thoroughly
already so I'm comfortable it'll do that just fine.
On 04/08/2019 18:12, Tom Glod via use-livecode wrote:
> Hi Alex, yes that would definitely be a great option for a high performance
> solution that would work well in the background.
> I did tests on such a solution a while back (for a similar task), but found
> that the httpd library was not able to receive large pieces of binary
> data. It worked beautiful with small chunks.
> So I don't know if it was me, if it was a missing feature in the library,
> but I will be investigating it again soon enough.
> Thanks for the reminder
> On Sun, Aug 4, 2019 at 9:59 AM Alex Tweedly via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>> OK, here's a "really out there" suggestion ....
>> 1. Run a local web server to serve files (locally only).
>> Can be done various ways, including (easily) via LC and the httpd
>> (build that server as a standalone and have it running -
>> started from your app if need be...)
>> 2. in your stack, just do
>> load url ("http://localhost:8080/myfilename") with message "mycallback"
>> and handle the file once it has been read in the "mycallback" handler
>> -- Alex.
>> On 04/08/2019 01:56, Tom Glod via use-livecode wrote:
>>> Hey folks,
>>> I'm having trouble finding a combination of settings that allows my file
>>> loading to seem to happen in the background.
>>> repeat while read_result is not "eof"
>>> read from file ThisFile for (1024 * 1000) bytes
>>> put the result into read_result
>>> put it after IntoThisVariable
>>> add length(it) to amount_read
>>> TSTProgress amount_read,ExpectedSize,"%","Loading File ..."
>>> (Progress Indicator Handler)
>>> wait 10 milliseconds with messages
>>> end repeat
>>> no matter what I try, its still sluggish, and it seems like messages are
>>> still accumilating instead of being processed by the engine.
>>> Am I missing something? Normally waiting with messages sufficiently
>>> the engine to allow the UI to remain responsive.
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode