TS Net for Indy vs Business
roger.e.eller at sealedair.com
Fri Dec 30 06:40:18 EST 2016
I am really disappointed that SFTP (for Indy) is limited to a variable
(RAM) -vs- writing directly to a file. Moving large files that exceed
system RAM is very common.
On Dec 30, 2016 5:13 AM, "Charles Warwick" <charles at techstrategies.com.au>
> Hi Andre,
> I will be adding a fair amount of documentation for tsNet over the coming
> weeks that I hope will better answer a number of the questions that are
> being asked on the list.
> In the mean time, I hope that the following two points will explain what
> is happening for you.
> 1. For Indy users, SFTP and SMTP can only be performed in "blocking"
> This means if you call any of the non-blocking variants of the libUrl or
> tsNet commands/functions with these protocols, you will get an error.
> For libUrl commands, non-blocking commands are:
> "load url", "libUrlDownloadToFile", "libUrlFtpUpload",
> For tsNet commands, non-blocking functions are:
> "tsNetGet", "tsNetGetFile", "tsNetUpload", "tsNetUploadFile", "tsNetSmtp",
> "tsNetSmtpFile", "tsNetSendCmd", "tsNetPost", "tsNetHead", "tsNetCustom"
> 2. For Indy users, SFTP and SMTP can only be performed to/from a variable
> - not directly using a file.
> This means you will also get an error if you use any of the blocking
> functions which directly reference a file when using these protocols.
> For tsNet, these functions are:
> "tsNetGetFileSync", "tsNetUploadFileSync", "tsNetSmtpFileSync"
> On 28/12/2016 5:31 AM, Andre Garzia wrote:
>> Yes, we found that page as well. The problem is that even though the page
>> lists features available to each license, there is no list of commands and
>> functions per license. For example, it says that public key authentication
>> is only available to business license holders, so we'd assume that if we
>> call tsNetUploadFileSync passing a username and password as an SFTP URL,
>> should work but it doesn't. Then we'd look into the docs and see that we
>> can pass a settings array with username and password which also doesn't
>> When I say "doesn't work", I don't mean it is buggy, I mean it returns an
>> error saying the external is unlicensed. Which will probably make me
>> fallback to using shell commands to scp/sftp/rsync or whatever I need to
>> make file transfers.
>> This "escalation of features" for file transfers based on your license for
>> me is cumbersome as I am more prone to use other solutions than stay
>> LC but this is a whole different thread.
>> What I think would be useful and not disruptive to HQ business model is
>> more info about this license limitations inside the LC dictionary. When
>> look at a given entry there, you don't see this info.
>> om om
>> PS: It has been a while hasn't it?
>> On Tue, Dec 27, 2016 at 7:32 AM, Richard Gaskin <
>> ambassador at fourthworld.com>
>> Sannyasin Brahmanathaswami wrote:
>>> We need some help.
>>>> We know that we can do SFTP with TS-Net external
>>>> functions that we try to use from an Indy LC return "unlicensed" even
>>>> when, the documentation make not indication that they should fail
>>>> without the business license.
>>>> What we need is
>>>> Documention on what functions and methods work for SFTP in Indy.
>>> There's probably a more intuitive taxonomic placement for this (though
>>> admittedly I can't decide on one offhand - suggestions?), but I poked
>>> around the livecode.com site and discovered that if I click "Pricing"
>>> then about the middle of the price comparison page is a link labeled
>>> "Compare Networking Fearures", which leads to this page that offers a
>>> breakdown by edition:
>>> Richard Gaskin
>>> Fourth World Systems
>>> Software Design and Development for the Desktop, Mobile, and the Web
>>> Ambassador at FourthWorld.com http://www.FourthWorld.com
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode