On 2015-08-20 00:12, Lyn Teyla wrote:
But that's just it — the network/sockets revamp using open language
(presumably LCB) *is* one of the items on the roadmap from the
Kickstarter campaign. While SFTP isn't specifically mentioned, that
"generally-useful LCB URL library" is. Here's the roadmap a
Peter TB Brett wrote:
> On 2015-08-19 21:53, Lyn Teyla wrote:
>
>> If a libCurl wrapper using LCB is in development, wouldn't the above
>> be a non-issue? That is, adding SFTP (or any other libCurl-supported
>> protocol) shouldn't need to involve writing and testing a lot of new,
>> security-crit
On 2015-08-19 21:53, Lyn Teyla wrote:
If a libCurl wrapper using LCB is in development, wouldn't the above
be a non-issue? That is, adding SFTP (or any other libCurl-supported
protocol) shouldn't need to involve writing and testing a lot of new,
security-critical code, since libCurl has already
On Wednesday, August 19, 2015, Peter TB Brett
wrote:
> On 2015-08-19 20:27, Lyn Teyla wrote:
>
> Have you guys at LiveCode Ltd thought about implementing this revamp
>> of networking/sockets by simply writing a libCurl wrapper using
>> LiveCode Builder?
>>
>
> Yes -- one of our very first, high p
Peter TB Brett wrote:
> On 2015-08-19 20:27, Lyn Teyla wrote:
>
>> Have you guys at LiveCode Ltd thought about implementing this revamp
>> of networking/sockets by simply writing a libCurl wrapper using
>> LiveCode Builder?
>
> Yes -- one of our very first, high priority ideas for an LCB-based p
On 2015-08-19 20:27, Lyn Teyla wrote:
Have you guys at LiveCode Ltd thought about implementing this revamp
of networking/sockets by simply writing a libCurl wrapper using
LiveCode Builder?
Yes -- one of our very first, high priority ideas for an LCB-based
project. I even made a start on it,
Peter TB Brett wrote:
> The LiveCode engine can already do secure communication using SSL (Secure
> Socket Layer). It would *probably* be possible to use "secure socket" to
> implement FTPS (FTP over SSL) in scripts, without any engine changes (i.e. in
> libUrl).
Given the following
