thank you guys for clearing that up for me, and future users who may ask
about this.
On Fri, Jun 16, 2017 at 1:38 AM, Charles Warwick via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 16/06/2017 2:39 PM, Monte Goulding via use-livecode wrote:
>
>> On 16 Jun 2017, at 2:22 pm, Tom Glod
On 16/06/2017 2:39 PM, Monte Goulding via use-livecode wrote:
On 16 Jun 2017, at 2:22 pm, Tom Glod via use-livecode
wrote:
I'm relieved to hear that I think I misunderstood Todd's blog... maybe
his was a purely volume related bottleneck and not the library
> On 16 Jun 2017, at 2:22 pm, Tom Glod via use-livecode
> wrote:
>
> I'm relieved to hear that I think I misunderstood Todd's blog... maybe
> his was a purely volume related bottleneck and not the library he was using.
Ah, yes his is a use case that had lots
>> all the reading and writing is done on a separate thread. Of course your
>> callback handler is handled on the main engine thread but that’s not the
>> slow part so that’s fine.
>>
>> tsNet does not provide sockets so that and its licensing probably only
>>
long as you use the callback (with message) form then
> all the reading and writing is done on a separate thread. Of course your
> callback handler is handled on the main engine thread but that’s not the
> slow part so that’s fine.
>
> tsNet does not provide sockets so t
lback
handler is handled on the main engine thread but that’s not the slow part so
that’s fine.
tsNet does not provide sockets so that and its licensing probably only confuses
any discussion of asynchronous sockets.
Cheers
Monte
___
use-livecode maili
Hi everyone,
I'm an open-source user and I am building socket communications for my
application.
I'm aware of the built in internet library and the tsNet library available
to non-open source license owners.
My question is "What isn't asyncronious about reading from and writing to
sockets?"
is