I missed the local db part. It is clearly written in your original email. But, 
since I am here typing these chars…pondering…how about running a local server 
that accesses your local db and use tsnet to do async calls?

Best regards,

Mark Talluto
livecloud.io <http://livecloud.io/>
nursenotes.net <http://nursenotes.net/>
canelasoftware.com <http://www.canelasoftware.com/>


> On Jun 14, 2018, at 12:45 PM, Ralph DiMola via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> I was referring to a local mobile SQLite DB query. But I do use async tsNet 
> for web service requests. It works like a charm even with many requests 
> outstanding. I fire up 10 or more at a time and they all compete as expected. 
> Async tsNet +1
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> 
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
> Of Mark Talluto via use-livecode
> Sent: Thursday, June 14, 2018 2:21 PM
> To: How to use LiveCode
> Cc: Mark Talluto
> Subject: Re: Anything LiveCode Can Learn From GO
> 
> tsNet with async calls can help you get this.
> 
> Best regards,
> 
> Mark Talluto
> livecloud.io <http://livecloud.io/>
> nursenotes.net <http://nursenotes.net/>
> canelasoftware.com <http://www.canelasoftware.com/>
> 
> 
>> On Jun 14, 2018, at 8:24 AM, Ralph DiMola via use-livecode 
>> <use-livecode@lists.runrev.com> wrote:
>> 
>> I would love to be able to start a thread that formatted a field that might 
>> be selected and made visible at a later date or have a scrolling field that 
>> could have the non-visible lines being formatted in another thread before 
>> you scroll down. Say you were going to a new card that required a DB query. 
>> You could have the card layout code and the query to a local DB running at 
>> the same time. Even with LCs message hierarchy multithreading could work. 
>> You could fire off a DB query thread and have a message sent to the main 
>> thread when complete. Inter thread communication would be key. That is where 
>> locking would be tricky to prevent dead locks.
>> 
>> Ralph DiMola
>> IT Director
>> Evergreen Information Services
>> rdim...@evergreeninfo.net
>> 
>> -----Original Message-----
>> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
>> Of Bob Sneidar via use-livecode
>> Sent: Thursday, June 14, 2018 10:56 AM
>> To: How to use LiveCode
>> Cc: Bob Sneidar
>> Subject: Re: Anything LiveCode Can Learn From GO
>> 
>> Multithreading sounds like a good idea until you realize most things that 
>> have to happen in Livecode due to the message heirarchy need to be single 
>> threaded. It's only when you need to make a server of some sort that 
>> multithreading really needs to be implemented. 
>> 
>> Bob S
>> 
>> 
>>> On Jun 11, 2018, at 17:08 , Sannyasin Brahmanathaswami via use-livecode 
>>> <use-livecode@lists.runrev.com> wrote:
>>> 
>>> I wasn't thinking about high language per se.   but more from an engine 
>>> point of view, specifically use of "Goroutines"
>>> 
>>> "But, most of the modern programming languages(like Java, Python etc.) are 
>>> from the ’90s single threaded environment. Most of those programming 
>>> languages supports multi-threading. But the real problem comes with 
>>> concurrent execution, threading-locking, race conditions and deadlocks. 
>>> Those things make it hard to create a multi-threading application on those 
>>> languages.
>> 
>> _______________________________________________
>> 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
> 
> 
> _______________________________________________
> 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

Reply via email to