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
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
Thank you for the clarification.
Kee Nethery
> On Feb 25, 2021, at 10:06 AM, Richard Gaskin via use-livecode
> 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
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
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?
Kee Nethery
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
Tom Glod wrote:
My goal is to be able to outsource the cloud services entirely I know
digital ocean has managed kubernetes and I can choose to use that.
So yes, if LC S3 library is corrected, then that would be my chosen option
Minio on managed kubernetes.
Otherwise I think WebDAV will be a
My goal is to be able to outsource the cloud services entirely I know
digital ocean has managed kubernetes and I can choose to use that.
So yes, if LC S3 library is corrected, then that would be my chosen option
Minio on managed kubernetes.
Otherwise I think WebDAV will be a second
Tom Glod wrote:
> Richard Gaskin wrote:
>> If WebDAV could work for your needs there are at least three FOSS
>> WebDAV libs for LC on Github - here are the forum posts where I
>> learned about them, with links to the repos (IIRC all three are
>> MIT License):
>>
>> With tsNet:
>>
Paul, thanks for your thoughts, you are right there are some traps with the
s3 compatible part, and some unknown that we may not know about.
Richard, thanks for letting me know about those libraries, its definitely
another option that can be used to achieve the same result. I will
definitely look
Thanks for that background, Tom.
If it *must* be s3 then either working with LC Ltd or crafting an open
competing lib would be necessary. Open source competing libs are
problematic on both sides, since the dev needs to replicate the effort
and the company loses one more advantage to their
he moment realizing that our AWS library only
> > works on amazon.
> >
> > Is there currently any workaround for using the AWS S3 library with s3
> > compatible hosts?
> >
> > Its beyond me why the endpoints needed to be hardcoded and require EXPERT
> &
ack is password protected.
> >
> > Thanks,
> >
> > Tom
> >
> > On Wed, Feb 24, 2021 at 2:52 PM Richard Gaskin via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> >
> >> Tom Glod wrote:
> >>
> >> > I'm r
ing that our AWS library only
> works on amazon.
>
> Is there currently any workaround for using the AWS S3 library with s3
> compatible hosts?
>
> Its beyond me why the endpoints needed to be hardcoded and require EXPERT
> REVIEW to implement a function to change the endpoi
On 2/24/2021 4:23 PM, Richard Gaskin via use-livecode wrote:
I would imagine adding optional args for new endpoints would be
simple to do, and open the package up to MANY more use cases.
This may not be an issue with the folks at LiveCode, Ltd, but one
possible reason why the library for
S library
> only works on amazon.
>
> Is there currently any workaround for using the AWS S3 library with s3
> compatible hosts?
>
> Its beyond me why the endpoints needed to be hardcoded and require
> EXPERT REVIEW to implement a function to change the endpoint.
Hard to g
use-livecode <
use-livecode@lists.runrev.com> wrote:
> Tom Glod wrote:
>
> > I'm really annoyed at the moment realizing that our AWS library
> > only works on amazon.
> >
> > Is there currently any workaround for using the AWS S3 library with s3
> >
Tom Glod wrote:
> I'm really annoyed at the moment realizing that our AWS library
> only works on amazon.
>
> Is there currently any workaround for using the AWS S3 library with s3
> compatible hosts?
>
> Its beyond me why the endpoints needed to be hardcoded and re
Hi Folks,
I'm really annoyed at the moment realizing that our AWS library only
works on amazon.
Is there currently any workaround for using the AWS S3 library with s3
compatible hosts?
Its beyond me why the endpoints needed to be hardcoded and require EXPERT
REVIEW to implement a function
18 matches
Mail list logo
