Re: using send to "multi-task" ? [was: Non-blocking URL commands]

2012-11-20 Thread Dr. Hawkins
On Mon, Nov 19, 2012 at 11:40 AM, Robert Sneidar wrote: > No that isn't how it works. That is what I thought as well. Send in time > really means >"do this after you have done everything else that is not send in time". The >command will >still be a blocking command. I thought it was too good to

Re: Non-blocking URL commands

2012-11-19 Thread Jan Schenkel
sh at the same time." (La Rochefoucauld) - Original Message - From: Andrew Kluthe To: How to use LiveCode Cc: Sent: Monday, November 19, 2012 5:19 PM Subject: Re: Non-blocking URL commands Hmmm. I gave that a whirl and am still getting an empty payload on windows 7 (the only machi

Re: using send to "multi-task" ? [was: Non-blocking URL commands]

2012-11-19 Thread Robert Sneidar
No that isn't how it works. That is what I thought as well. Send in time really means "do this after you have done everything else that is not send in time". The command will still be a blocking command. If you really want asynchronous database processing, save your query to a text file, then

Re: Non-blocking URL commands

2012-11-19 Thread Andrew Kluthe
ooOooo. :) Let me know if I can lend a hand down the road. We use mongoDB for some of our farm management software because of the handy geospacial features. If it helps you or anyone else, I have a library that wraps around MongoLab's REST interface. Mongolab has really excellent support and is the

Re: Non-blocking URL commands

2012-11-19 Thread Richard Gaskin
Mark Wieder wrote: I have a fledgling LC MongoDB library, but it isn't polished enough yet for revOnline. I took the easy way out and used the commandline interface, though. That's pretty exciting. While I haven't used MongoDB much myself yet, I've been spending a fair bit of time reading it

Re: Non-blocking URL commands

2012-11-19 Thread Mark Wieder
Andrew Kluthe writes: > I wish I were more familiar with socket programming in rev and socket > programming in general. What I really need to do is write a native > MongoDB driver for livecode, so I don't have to use a REST interface. > The specifications are laid out very nicely, but unfortunate

Re: Non-blocking URL commands

2012-11-19 Thread Andrew Kluthe
La Rochefoucauld) > > > - Original Message - > From: Andrew Kluthe > To: How to use LiveCode > Cc: > Sent: Sunday, November 18, 2012 8:36 PM > Subject: Re: Non-blocking URL commands > > Jan, > > Is there an equivalent to libUrlSetSSLVerification false with

Re: Non-blocking URL commands

2012-11-18 Thread Jan Schenkel
me." (La Rochefoucauld) - Original Message - From: Andrew Kluthe To: How to use LiveCode Cc: Sent: Sunday, November 18, 2012 8:36 PM Subject: Re: Non-blocking URL commands Jan, Is there an equivalent to libUrlSetSSLVerification false with your library? The rest interface I want to

Re: Non-blocking URL commands

2012-11-18 Thread Andrew Kluthe
we grow older, we grow both wiser and more foolish at the same time." >> (La Rochefoucauld) >> >> >> >> - Original Message - >> From: Andrew Kluthe >> To: How to use LiveCode >> Cc: >> Sent: Friday, November 16, 2012 10:30 PM >&

Re: Non-blocking URL commands

2012-11-18 Thread Andrew Kluthe
riginal Message - > From: Andrew Kluthe > To: How to use LiveCode > Cc: > Sent: Friday, November 16, 2012 10:30 PM > Subject: Non-blocking URL commands > > Man oh man, wouldn't it be nice to have a non-blocking http > implementation in livecode? Certain REST api call

using send to "multi-task" ? [was: Non-blocking URL commands]

2012-11-18 Thread Dr. Hawkins
On Fri, Nov 16, 2012 at 2:13 PM, Monte Goulding wrote: > It means other scripts can run but the script executing the post is blocked > waiting for it >to return. It's how your users manage to execute other things while the http >request is >going on. Disable anything you don't want them to do wh

Re: Non-blocking URL commands

2012-11-18 Thread Jan Schenkel
= Quartam Reports & PDF Library for LiveCode www.quartam.com = "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld) - Original Message - From: Andrew Kluthe To: How to use LiveCode Cc: Sent: Friday, November 16, 201

Re: Non-blocking URL commands

2012-11-16 Thread Monte Goulding
It means other scripts can run but the script executing the post is blocked waiting for it to return. It's how your users manage to execute other things while the http request is going on. Disable anything you don't want them to do while waiting. On 17/11/2012, at 8:59 AM, Andrew Kluthe wrote:

Re: Non-blocking URL commands

2012-11-16 Thread Andrew Kluthe
The crash just comes when it is taking a minute and the user tries to hit refresh again a couple of times or makes some other http request. Too many of those and my program stops responding on windows. Can you elaborate a little more on "wait with messages style blocking"? I am a bit dense today.

Re: Non-blocking URL commands

2012-11-16 Thread Monte Goulding
Hi Andrew Not sure about the crash. That should be reported. But because urls use wait with messages style blocking you can sort of do non-blocking urls if you send a message in time and have that command post to your URL. Cheers -- M E R Goulding Software development services mergExt - There

Non-blocking URL commands

2012-11-16 Thread Andrew Kluthe
Man oh man, wouldn't it be nice to have a non-blocking http implementation in livecode? Certain REST api calls with some services I use can lock and crash my applications if it takes to long to get a full response. Has this ever been something runrev has mentioned or talked about? -- Regards, An