unresponsive sequential post requests - libURL problem?

[Terry Judd]

On 01/03/2012, at 01:59 PM, Andre Garzia wrote:

Are these posts all going to the same server? Do you see something like
"error, the previous request is not complete" or similar? How many posts
are we talking about?

Hi Andrew - yes - all to the same server and yes - I often see the 'previous request not completed' message as well. When that occurs, I generally have to do the unspeakable and call resetAll to free things up again.

How many posts - well, single posts are generally OK but 2 or 3 in quick succession is often enough to cause problems. At the moment I'm just trying to stop any extra requests from being sent until the initial one has been dealt with satisfactorily.

Terry...


On Wed, Feb 29, 2012 at 9:51 PM, Terry Judd <tsj at unimelb.edu.au<mailto:tsj at unimelb.edu.au>> wrote:

Hi guys (Dave hopefully you're not too far away) - earlier on I asked
about explicitly closing sockets to try and prevent Livecode becoming
unresponsive following repeated post (over https) requests. Dave Cragg
suggested setting the httpHeaders to "Connection: close header". This
helped somewhat in that it allowed me to test for an open socket before the
next request was sent (initiated by a user clicking various controls in the
interface). If a socket was open then I simply ignored the user's clicks
until it was closed again.

However, it still doesn't solve the underlying problem, and if I do stack
up a few requests and Livecode typically becomes unresponsive (waiting for
a lengthy period rarely solves the problem) and the only way to 'clear the
pipes' is to hit command/control-period a couple of times. The first time
generally frees up the cursor again (set to a custom cursor when the
request is initiated) while the second time usually triggers an error
message along the lines of...

error: 624,1521,1 (or slight variations on this)

...to be returned in the result following the post request.

This (possibly naively) leads me to think that the underlying problem
might lie somewhere within libURL, with a handler or function that is
reluctant to end. Is this possible? Any ideas or suggestions would be
greatly appreciated.

Terry...

Dr Terry Judd
Senior Lecturer in Medical Education
Medical Eduction Unit
Faculty of Medicine, Dentistry & Health Sciences
The University of Melbourne



_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
http://www.andregarzia.com -- All We Do Is Code.
http://fon.nu -- minimalist url shortening service.
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Dr Terry Judd
Senior Lecturer in Medical Education
Medical Eduction Unit
Faculty of Medicine, Dentistry & Health Sciences
The University of Melbourne