pete at lcsql.com
Fri Sep 18 15:06:36 EDT 2015
I ended up issuing resetAll which seemed to fix the problem.
On Fri, Sep 18, 2015 at 11:45 AM Richard Gaskin <ambassador at fourthworld.com>
> Peter Haworth wrote:
> > The dictionary says all actions that refer to a URL are blocking but if I
> > execute:
> > put URL myURL into tResults
> > ... my handler immediately goes to the next statement and tResuls
> > "error URL is currently loading".
> > The url is question is to an api so I guess the error could be coming
> > there but all the error messages I've received have been wrapped in XML.
> We really need some clarity on this. I've been using LC for years, but
> whatever rules might allow me to anticipate whether network I/O is
> blocking or non-blocking have eluded me in practice.
> These days I almost always rely on callbacks, since I know those are
> always non-blocking, though even then I'm not sure of the implications
> in terms of overall performance, given that it provides us the illusion
> of concurrency but without true parallelism.
> Could someone on the core team draft a page that would help us
> understand network I/O in terms of blocking and non-blocking, and how
> non-blocking code is handled in a single-threaded engine?
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> Ambassador at FourthWorld.com http://www.FourthWorld.com
> 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