I've used load for this in the past. The ability to specify a callback message makes it work well. In my case I was experimenting with offloading a large job to a webserver for processing. To help with organizing the data being returned, I tacked a # and an incrementing number to the end of each url. Made it easy to re-assemble things into the proper order. (Be aware though, things behave differently between desktop and mobile so you have to take platform into account)
On Thu, Mar 15, 2018 at 8:26 PM, Tom Glod via use-livecode < use-livecode@lists.runrev.com> wrote: > i need to be able to send more than one http request to my cloud service > domain at one time....it is not a limitation I am willing to live with > ....and I don't want to package requests together and have to wait for all > of them to be processed before something comes back. > > Its not a limitation that should exist in any modern software..... and it > won't in mine...... so I have to try different ways to try to get around > this somehow and still be GPL3 > > Cheers....I'm going to try the read from process idea....and see if i can > read the returned requests faster that way. > > Thank you. > > > > > > > On Thu, Mar 15, 2018 at 10:14 PM, Richard Gaskin via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > Tom Glod wrote: > > > Hi guys, I've brought this up before.....and the time to solve is > > > coming sooner than I expected. > > > > > > 1. My project must be open source > > > 2. I must communicate with cloud service not one request at a time. > > > 3. TsNet is not open source and I love that LC has a feature that > > > can bring them important revenue. > > > > > > But I have to create a workaround ... so its hackathon time.... > > > > > > My first idea is to do this : > > > > > > - Create process in Go using Go Routines to give me concurrent http > > > requests > > > - send all my requests to that process via a non-blocking socket > > > - read from the socket in non-blocking way to receive the data > > > returned > > > for the requests until all requests have completed or timed out. > > > > While it is unfortunate that LC is among the few open source languages > > that doesn't have CURL support, in your case I wonder if it's truly > > necessary. > > > > The engine's socket support is generally pretty good, and libURL can be > > modified. What exactly do you need to do? > > > > -- > > Richard Gaskin > > Fourth World Systems > > Software Design and Development for the Desktop, Mobile, and the Web > > ____________________________________________________________________ > > ambassa...@fourthworld.com http://www.FourthWorld.com > > > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
