non-blocking http ... will tsnet end up in community?

Alex Tweedly alex at tweedly.net
Tue Dec 19 17:49:25 EST 2017


I think that, unfortunately, it's not going to be possible.

I am 99% sure that I remember, either in the initial announcement or 
closely related to it, that Kevin mentioned that they (Livecode Ltd) pay 
a per-user (i.e. per-licence) fee to the third party for each tsNet - 
which means they have no way to be able to release it under the 
Community agreements.

Alex.


On 19/12/2017 20:13, Tom Glod via use-livecode wrote:
> Hi Matthias... thank you for your thoughts.
>
> I think my post was less about my own needs for that feature .... but in
> general I'm seeing that Web API's are getting more and more capable and
> will be more and more used by developers going forward.  So being unable to
> send more than one asyncronoys request to the same server is highly
> limiting.
>
> So if livecode has any hope that their platform will ever be used for a
> serious and extensive open source project, this is a deal breaker.
>
> As for me, I think I can work around this for my needs. .... for now.  Like
> I said, I have no choice in using the community version, so I'm not
> conflicted as to what to do .... just gotta go forward.
>
> Thanks for your thoughts and Cheers,
>
> Tom
>
>
>
> On Tue, Dec 19, 2017 at 7:45 AM, Matthias Rebbe via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> Tom, please excuse for using the wrong name.
>>
>> Von meinem iPhone gesendet
>>
>>> Am 19.12.2017 um 13:13 schrieb Matthias Rebbe via use-livecode <
>> use-livecode at lists.runrev.com>:
>>> Todd,
>>> i understand your desire to have such a feature in the Community
>> Edition, but I don´t think this will happen in near future.
>>> If i understood correctly then tsNET is a 3rd party product which
>> Livecode Ltd. has acquired or however this is called. So they have paid
>> money for that.
>>> The tsNet external is really a big win for us and i think it is just
>> fair that this is only included in the commercial licenses.
>>> Why? Because there must be a difference between a free license and a
>> paid license otherwise everyone would use the free one.
>>> And there must be  a feature difference between different Indy and
>> Business license t for the same reason.
>>> Btw. Xojo does it the same.  The more you pay, the more you´ll get. With
>> one exception, they are not offering a free version.
>>> LibURL does and did its job more or less well for years. So at least
>> there is the possibility to do asnynchronous operations.
>>> Although i am a 1-man company and my revenues are less than $500,000 a
>> year and although i have a lifetime Indy license  i
>>> have subscribed for a business license just because of its features and
>> the possibility to get priority support if ever needed.
>>> The indy license btw.allows only 1 seat per organisation. A Seat
>> (regardless if Indy or Business) are for one named developer and
>>> cannot be shared. If you need more seats you have to purchase a business
>> license with the appropriate number of seats.
>>> It seems not all customers are/were aware of these terms in the past.
>> Otherwise Livecode Ltd. would not have sent out an email in October to all
>>> Indy/Business customers with some information about the license terms
>> and the requirement to sign a digital license agreement.
>>> What i would vote for is to add SFTP (synchronous) feature to the
>> Community Edition to allow secure FTP transfers.
>>> Matthias
>>>
>>>
>>>> Am 19.12.2017 um 00:50 schrieb Tom Glod via use-livecode <
>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>:
>>>> Hi Everyone,
>>>>
>>>> I use the Community version for project, and recently I've been working
>>>> with the LibURL Library to get some asynchronous server client
>>>> communication going ...and if you've ever worked with that ...... its
>> clear
>>>> there is much room for improvement there.
>>>>
>>>> Though I have no choice what version to use, so I can only wait in
>>>> patience, but I think for the long term health of the platform and to
>> give
>>>> it the modern robustness it needs, the tsnet library is going to have to
>>>> become part of the community version.  Otherwise it will always lag
>> behind
>>>> from being able to use modern internet APIs in combination.
>>>>
>>>> Is this something we would have to crowd fund?
>>>>
>>>> Is there anything legally preventing that from happening?
>>>>
>>>> Thanks for any thoughts
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>
>>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> Matthias Rebbe
>>> Tel +49 5741 310000
>>>https://matthiasrebbe.eu <https://matthiasrebbe.eu/>‌
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list