Thanks Mike / Richard. Brief comments below:
On 20 July 2015 at 17:33, Mike Kerner wrote:
> The main reason for doing things asynchronously are
> 1) to improve performance in a high-transaction environment
> 2) keep collisions to a minimum.
>
> In your case, it does not appear that either is goi
The main reason for doing things asynchronously are
1) to improve performance in a high-transaction environment
2) keep collisions to a minimum.
In your case, it does not appear that either is going to happen, so I
wouldn't bother.
On Mon, Jul 20, 2015 at 12:03 PM, Richard Gaskin wrote:
> David
David Bovill wrote:
>- Is it worth designing a Livecode server to use asynchronous
> calls to handlers rather than normal synchronous processing?
>
> First off - the way this is going to be done will not use any io
> (file, shell or internet / socket calls) - all the data is going
> to be in
I have a question for any of you out there that know a thing or two about
synchronous vs asynchronous design:
- Is it worth designing a Livecode server to use asynchronous calls to
handlers rather than normal synchronous processing?
First off - the way this is going to be done will not use
