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

2017-12-20 Thread Tom Glod via use-livecode
It makes perfect sense that it is a strong reason to get a business license
...I have full respect as to why it currently is not part of the community
edition.  i also understand that for a lot of use cases, its perfectly
fine.  Just not in mine.

Having said that, there has to be a solution, so the one I see in my mind
is to use a process (written in Go (or copy and pasted is more like it)) to
send the requests and receive the responses and give it back to me via a
local socket  no idea what performance will be like but it will be
better than what is there now as far as trying to have high performance
async http.

I'm all ears if someone has a better idea.

I  appreciate everyone's thoughts on this  lots to think about when
making decisions about things.
___
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


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

2017-12-20 Thread Richard Gaskin via use-livecode

andrew at midwestcoastmedia.com wrote:

>> DDoS tools aside , what APIs need more than one call at a time?
>>
>
> I can think of a use in my (relatively) simple Indiana On Tap mobile
> app. Currently I fetch some mySQL data and download some images from a
> HostM account through their SSL API. The data is a couple of arrays
> with a 30-300 entries each and the images are between 5KB-200KB.
> Sometimes these fire off super fast back-to-back-to-back finishing in
> 3 or 4 seconds, but other times there is a network lag (I've scripted
> some tests and determined it isn't the app or the server process) and
> the entire process takes up 25 seconds.
>
> Just recently while testing some REST stuff I discovered how to do the
> async tsNet calls (I second whomever suggested crowd funding Charles
> to write some tutorial stacks!). I think by calling these commands
> async will allow me to speed up the app initialization process: no
> waiting for server reply between each request so I can move onto the
> 1st non-splash card of the app.
>
> The speed increase and ability to make multiple concurrent
> non-blocking calls is also the key to allowing "Enable Background
> Execution" of this app. This unexpected bonus benefit is YUGE as that
> has been a complaint about the app.

Good example there, Andrew.  Thanks for that.

I had a loosely-related need that isn't so much germain to this 
discussion as just another story of how LC's flexibility can impress 
people in the enterprise world where all they know is Java:



One of the client-server systems I've delivered includes a media 
management library, where users can upload, modify, and select media 
files from a collection of ~3,000 JPEG and MP4 files.


To provide the UI for that I wanted the list view to include thumbnails, 
but of course early on I realized I didn't want 3,000 separate HTTP 
requests to populate it.


After playing around with a few different combinations of JPEG quality 
and resizing, I finally arrived at a solution that fit all those 
thumbnails into a single compressed LSON file.


Between the image compression already in the JPEG data and the 
efficiency of Gzip for the array key names and metadata, the entire 
thumbnail archive takes up a mere 1.1 MB.


So when our users open the media library, a single request to the server 
for a one-meg file populates a richly-visual DataGrid with thousands of 
items, all in just a couple seconds.  From there they can filter and 
select flexibly, easily, and rapidly, since the entire archive is now 
local in RAM.


Experimentation, deployment, and testing for both client and the 
server-side stuff to maintain the thumbnails took less than a day.


Meanwhile, another team working for the same company was making a 
similar subsystem for another product, but in Java.  Somehow putting all 
the thumbnails into a single array didn't occur to them, instead taking 
the more common route of getting each one in a separate HTTP request, 
and then having to use paging to limit the number of items that can be 
seen on screen at any given time.


At the end of the day, they spent a heckuva lot more on their UI than I 
did on mine, and their users complain that it's slow and limited.


I've tried suggesting LC to that team, but you know how it goes: "But 
Java is the standard." ;)


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://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


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

2017-12-20 Thread Richard Gaskin via use-livecode
Excellent thinking, Charles.  Thanks for chiming in.  Most of my net 
work has been on projects where I deliver both client and server, so 
I've too often had the luxury of working with APIs of my own design. 
You raise some good considerations there.


Given the value of multiple connections, beyond replicating your 
excellent work with tsNet from scratch what would you recommend for 
developers in our community like Tom who prefer to release their work 
under GPL license?


--
 Richard Gaskin
 Fourth World Systems


Charles Warwick wrote:

> Hi Richard,
>
>> Is it?
>>
>> DDoS tools aside , what APIs need more than one call at a time?
>
> Not that I am Tom, but many APIs need different calls to retrieve
> various pieces of information.  Just as a simple example, if you are
> writing a weather app and you want to display on one screen the
> temperatures for multiple cities, you may have to make an API call for
> each city before you can render the entire screen.
>
>> And since LC is single-threaded, what do you anticipate doing with
>> the data from the multiple requests as it comes in?
>
> The issue is usually that API calls can take time for the server to
> respond.  By executing them in series, if you had to make 10 calls and
> each one takes 500ms, that is 5 seconds of delay.
>
> If you can send all 10 requests at once, you are likely to be waiting
> less than 1 second in total - which makes a significant improvement
> for user experience.
>
>> This is a serious question.  Most of my work is with small data
>> (<200k) where latency even on shared hosts is minimal.  But needs
>> vary.  I'm interested in understand the problem you're facing.
>>
>
> This may not be the problem Tom is facing, but it is one I deal with
> regularly.
>
> Cheers.
>
> Charles




___
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


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

2017-12-20 Thread Andrew Bell via use-livecode

DDoS tools aside , what APIs need more than one call at a time?



I can think of a use in my (relatively) simple Indiana On Tap mobile  
app. Currently I fetch some mySQL data and download some images from a  
HostM account through their SSL API. The data is a couple of arrays  
with a 30-300 entries each and the images are between 5KB-200KB.  
Sometimes these fire off super fast back-to-back-to-back finishing in  
3 or 4 seconds, but other times there is a network lag (I've scripted  
some tests and determined it isn't the app or the server process) and  
the entire process takes up 25 seconds.


Just recently while testing some REST stuff I discovered how to do the  
async tsNet calls (I second whomever suggested crowd funding Charles  
to write some tutorial stacks!). I think by calling these commands  
async will allow me to speed up the app initialization process: no  
waiting for server reply between each request so I can move onto the  
1st non-splash card of the app.


The speed increase and ability to make multiple concurrent  
non-blocking calls is also the key to allowing "Enable Background  
Execution" of this app. This unexpected bonus benefit is YUGE as that  
has been a complaint about the app.


--Andrew Bell


___
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


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

2017-12-20 Thread Tom Glod via use-livecode
Charles gave a perfect example of 1 api that could easily be called more
than once.

Another example is syncing files to dropbox, but also attempting to
download one at the same time, or even just updating the list of files in
the folder as it may be syncing files.  also, using any of google's api's
in combination will be problematic if not just slow.

As I said, this is not a requirement for my current project, but for the
next one, it will be.  The platform will be able to integrate many apis so
it is very likely that one at a time will not do, even if i don't know the
specifics yet.

i have a plan for a kind of workaround for this limitation by using Golang
as the API caller and using "open process" to talk to it (which can be
asynchronous as far as I know).  the overhead should be manageable there.
we shall see.

Thank you both


On Wed, Dec 20, 2017 at 4:27 AM, Charles Warwick via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Richard,
>
> > Is it?
> >
> > DDoS tools aside , what APIs need more than one call at a time?
>
> Not that I am Tom, but many APIs need different calls to retrieve various
> pieces of information.  Just as a simple example, if you are writing a
> weather app and you want to display on one screen the temperatures for
> multiple cities, you may have to make an API call for each city before you
> can render the entire screen.
>
> > And since LC is single-threaded, what do you anticipate doing with the
> data from the multiple requests as it comes in?
>
> The issue is usually that API calls can take time for the server to
> respond.  By executing them in series, if you had to make 10 calls and each
> one takes 500ms, that is 5 seconds of delay.
>
> If you can send all 10 requests at once, you are likely to be waiting less
> than 1 second in total - which makes a significant improvement for user
> experience.
>
> > This is a serious question.  Most of my work is with small data (<200k)
> where latency even on shared hosts is minimal.  But needs vary.  I'm
> interested in understand the problem you're facing.
> >
>
> This may not be the problem Tom is facing, but it is one I deal with
> regularly.
>
> Cheers.
>
> Charles
>
>
> > --
> > Richard Gaskin
> > Fourth World Systems
> > Software Design and Development for the Desktop, Mobile, and the Web
> > 
> > ambassa...@fourthworld.comhttp://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


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

2017-12-20 Thread Charles Warwick via use-livecode
Hi Richard,

> Is it?
> 
> DDoS tools aside , what APIs need more than one call at a time?

Not that I am Tom, but many APIs need different calls to retrieve various 
pieces of information.  Just as a simple example, if you are writing a weather 
app and you want to display on one screen the temperatures for multiple cities, 
you may have to make an API call for each city before you can render the entire 
screen.

> And since LC is single-threaded, what do you anticipate doing with the data 
> from the multiple requests as it comes in?

The issue is usually that API calls can take time for the server to respond.  
By executing them in series, if you had to make 10 calls and each one takes 
500ms, that is 5 seconds of delay.

If you can send all 10 requests at once, you are likely to be waiting less than 
1 second in total - which makes a significant improvement for user experience.

> This is a serious question.  Most of my work is with small data (<200k) where 
> latency even on shared hosts is minimal.  But needs vary.  I'm interested in 
> understand the problem you're facing.
> 

This may not be the problem Tom is facing, but it is one I deal with regularly.

Cheers.

Charles


> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> 
> ambassa...@fourthworld.comhttp://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


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

2017-12-20 Thread Richard Gaskin via use-livecode

Tom Glod wrote:

> ...being unable to send more than one asyncronoys request to the same
> server is highly limiting.

Is it?

DDoS tools aside , what APIs need more than one call at a time?

And since LC is single-threaded, what do you anticipate doing with the 
data from the multiple requests as it comes in?


This is a serious question.  Most of my work is with small data (<200k) 
where latency even on shared hosts is minimal.  But needs vary.  I'm 
interested in understand the problem you're facing.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://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


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

2017-12-19 Thread Tom Glod via use-livecode
Hi Alex, thats interesting  thanks for that bit of information.  I'm going
to have to educate myself on this some more, maybe take a moment and write
to kevin to find out from the boss.

Cheers

On Tue, Dec 19, 2017 at 5:49 PM, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:

> 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@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@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@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
> 

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

2017-12-19 Thread Alex Tweedly via use-livecode

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@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@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@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@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 31
‌https://matthiasrebbe.eu ‌
___
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:

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

2017-12-19 Thread Tom Glod via use-livecode
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@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@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@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@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 31
> > ‌https://matthiasrebbe.eu ‌
> > ___
> > 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

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

2017-12-19 Thread Matthias Rebbe via use-livecode
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 
> :
> 
> 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 
>> >:
>> 
>> 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@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 31
> ‌https://matthiasrebbe.eu ‌
> ___
> 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

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

2017-12-19 Thread Matthias Rebbe via use-livecode
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 
> >:
> 
> 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@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 31
‌https://matthiasrebbe.eu ‌
___
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

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

2017-12-18 Thread Tom Glod via use-livecode
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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode