S3 API vs AWS

2021-02-28 Thread Mark Clark via use-livecode 
Since I posted the enhancement request for a non-AWS S3 endpoint, thought I 
might chime in a bit on S3. I worked with AB and Harsha (founders of Minio) in 
a past life when they were at Gluster (acquired by RedHat) and I was at a 
company called Compellent (acquired by DELL). Knowing those two I believed 
their notion of a developer-centric open source object store was a winning 
idea. 

Kevin and everyone at LiveCode get a *lot* of people pulling at them for 
attention. I’m in awe of their ability to do so much with relatively few 
resources. Back in 2016 they were tremendously busy, which is still true for 
2021:)

Currently I use Minio in a production environment and since LiveCode doesn’t 
natively support it, I wrote a simple server back end to handle client requests 
that require object. LiveCode is not what we use to build our products, but it 
sure has come in handy for prototyping our UI and doing IT style apps in the 
back office. 

In retrospect I should have banged the drums with the whole community and 
pushed this idea of putting some money behind the request. But those darn day 
jobs get in the way, sometimes.

Minio + LC = Goodness, even if you have to use shell and mc under the hood:)

Mark

From: Mark Clark 
Subject: 500 Dollar Pledge: Livecode plus S3 API (object storage)
Date: May 26, 2016 at 9:33:30 AM CDT
To: Kevin Miller 

Sorry if this is seemingly off topic to LiveCode, but it does help illustrate 
cloud storage opportunities for LC with the planned/eventual improved 
networking. Minio libraries are FOSS drop in replacements for S3 so no issues 
for LC in paid or open source versions. Files must go to object to overcome 
limits of RAID and filesystems, so how amazing would it be for LiveCode to 
include s3 (which for better or worse is now the defacto standard for object 
storage) native commands for getting and putting data to the cloud? LC is a 
perfect visual means of tying together various complicated sub-systems to 
generate a new generation of rich GUI web apps.

https://blog.minio.io/object-storage-in-practice-creating-a-reliable-data-store-9b424a22e8e#.5nyuf9by9
 


I have been happy to support each campaign along the way and will continue to 
believe in your vision for LiveCode. But I sometimes wonder if failing to 
support or at least post a vision for cloud scale data storage for app 
developers is a bit similar to not putting a network piece into Hypercard. 
Would you consider a campaign of say 10k to support a set of minio widgets for 
LiveCode? I would happily pay $500.00 towards such a project if you felt it 
worthwhile to put forward. 

Minio has three main components: a client and client libraries for accessing 
objects via S3; a single instance micro server for S3 (how cool if this were 
placed with LiveCode Server); and an XL version (still under heavy dev) which 
is a fully distributed and erasure encoded object storage server. 


Respectfully,

Mark Clark

> 
___
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: S3 Compatible?

2021-02-28 Thread Tom Glod via use-livecode 
Hi Andre,

Monte mentioned above that he didn't know about it at the time he created
the library,
and I guess no one needed it badly enough to request a feature enhancement
until September 24, 2020
I can't even imagine the number of things a development platform like lc
must keep track of to stay up to date.
I also wonder how many people in the world are truly familiar with the LC's
C++ source code.
2 maybe 3?


On Sun, Feb 28, 2021 at 7:25 AM Andre Garzia via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I think that a consequence of the popularity of S3 REST API was overlooked
> by the LC HQ when they designed the AWS library. Many of the AWS APIs were
> copied by other competing products so that they'd become a turn-key
> replacement for AWS. It is much easier to push your company's backuping
> solution if it is compatible to S3 for example. Many FOSS self-hosted
> projects created endpoints compatible with AWS for the same reasons.
>
> It should be trivial to add a command to register a custom endpoint. I
> think that the whole password protection of that stack is to make sure it
> is only available to Indy licensees. I don't mind it being Indy and up
> only, but I'd love for those libraries to have their source open so that
> people can contribute such small changes. This would free resources from
> the mothership and keep those libraries fresh.
>
> Best
> A
>
> On Thu, 25 Feb 2021 at 20:13, Kee Nethery via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Thank you for the clarification.
> >
> > Kee Nethery
> >
> > > On Feb 25, 2021, at 10:06 AM, Richard Gaskin via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> > >
> > > Kee Nethery wrote:
> > >
> > > > From this conversation am I to assume that if I am planning
> > > > on building a project that relies on AWS S3, I’m gonna have
> > > > to roll my own connector to it?
> > >
> > > It seems the opposite: if you need S3 storage, AWS is the only one
> > supported by the LC lib included in proprietary editions.
> > >
> > > You would only need to roll your own if you want S3 from another
> > provider, which is the circumstance Tom has which prompted this thread.
> > >
> > > Monte described the history of the library a couple posts back:
> > >
> http://lists.runrev.com/pipermail/use-livecode/2021-February/263537.html
> > >
> > > --
> > > 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
> >
>
>
> --
> https://www.andregarzia.com 
> Want to support me? Buy me a coffee at https://ko-fi.com/andregarzia
> ___
> 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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Mobile:647.562.9411
___
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: S3 Compatible?

2021-02-28 Thread Andre Garzia via use-livecode 
I think that a consequence of the popularity of S3 REST API was overlooked
by the LC HQ when they designed the AWS library. Many of the AWS APIs were
copied by other competing products so that they'd become a turn-key
replacement for AWS. It is much easier to push your company's backuping
solution if it is compatible to S3 for example. Many FOSS self-hosted
projects created endpoints compatible with AWS for the same reasons.

It should be trivial to add a command to register a custom endpoint. I
think that the whole password protection of that stack is to make sure it
is only available to Indy licensees. I don't mind it being Indy and up
only, but I'd love for those libraries to have their source open so that
people can contribute such small changes. This would free resources from
the mothership and keep those libraries fresh.

Best
A

On Thu, 25 Feb 2021 at 20:13, Kee Nethery via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thank you for the clarification.
>
> Kee Nethery
>
> > On Feb 25, 2021, at 10:06 AM, Richard Gaskin via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Kee Nethery wrote:
> >
> > > From this conversation am I to assume that if I am planning
> > > on building a project that relies on AWS S3, I’m gonna have
> > > to roll my own connector to it?
> >
> > It seems the opposite: if you need S3 storage, AWS is the only one
> supported by the LC lib included in proprietary editions.
> >
> > You would only need to roll your own if you want S3 from another
> provider, which is the circumstance Tom has which prompted this thread.
> >
> > Monte described the history of the library a couple posts back:
> > http://lists.runrev.com/pipermail/use-livecode/2021-February/263537.html
> >
> > --
> > 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
>


-- 
https://www.andregarzia.com 
Want to support me? Buy me a coffee at https://ko-fi.com/andregarzia
___
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