on-rev upload limits and Amazon S3 as an alternative

[David Bovill]

Mark Smith made some S3 libraries - trying to get hold of him is a little
futile :) I'm not sure where you can find them online - but I can send a
copy off list - I've not used them - this is from the README:

s3.setSecure
> command
>
> s3.setSecure true|false
>
> If set to true, https connections will be used, otherewise http.
> It's set to true by default
> see curl.setStrictSsl
> ----------
> s3.store
> command
> blocking
>
> s3.store objectKey, dataToStore, accessControl
>
> stores the given data to the object named.
>
> objectKey is the full name (including bucket) of the object you want to
> store the data in eg "someBucket/someObject"
>
> The data can be any kind of text or binary data.
>
> accessControl can be one of "private", "public-read", "public-read-write",
> "authenticated-read". If not specified, "private" is the default.
>
> If you want to upload a file directly from disc, then use the full path of
> the file you want to upload, and prefix it with "file:"
>
> put "/Users/me/Desktop/someFile.txt" into tFile
> s3.store "/someBucket/someFile.txt", "file:" & tFile
>
> If an error occurs, there will be a description in 'the result', which will
> otherwise be empty.
> ----------
> s3.fetch
> function
> blocking
>
> put s3.fetch(objectKey) into variable
> get s3.fetch(objectKey, destinationFile)
>
> objectName is the full name (including bucket) of the object you want to
> fetch eg. "someBucket/someObject"
>
> destinationFile (if used) is the full path to the file you want to put the
> downloaded data in.
>
> If no destination file is provided, the function simply returns the data,
> otherwise, it writes the data to the provided file.
>
> In either case, if there was an error, the description of the error is
> returned.
> ----------
> s3.info
> function
> blocking
>
> put s3.info() -- shows a list of your buckets
> put s3.info(bucketName) -- shows a list of the objects in a bucket
> put s3.info(objectKey) -- shows a list of properties of the object
>
> The properties listed for an object include:
>
> an md5 digest of the object
> the last modified date of the object in seconds (unix time)
> any meta-data that was attached to the object when uploaded.
> ----------
> s3.delete
> command
> blocking
>
> s3.delete objectKey
> s3.delete bucketName
>
> Deletes the specified object. If a bucket is specified, it will be deleted
> only if it is empty.
>
> The result will be set to empty on success, otherwise it will contain an
> error description.
> ----------
> s3.uploadFile.curl
> function
>
> put s3.uploadFile.curl(tObject, tFile) into tCurl.
> this creates a curl instance that is initialised and ready to upload the
> given file to the given bucket/object. The id of that curl instance is
> returned.
>
----------


On 28 January 2011 15:05, Martin Koob <mkoob at rogers.com> wrote:

>
> I have been testing uploading via post to on-rev and have found the limit
> is
> about 10.1 MB.  I was using movie files of various sizes and the largest I
> could successfully upload was 10.1 MB.  If I tried one of 10.2 Mb it would
> write a Quicktime file that had no data in it, it was  0 MB file.  If I
> tried to open it Quicktime gave a 'This is not a movie file' error.
>
> I guess this is a limit set in the on-rev server.
>
> As a way of accommodating larger file uploads for a site hosted on on-rev I
> am thinking of using Amazon S3.
>
> I want to use browser based uploads to have users upload a movie to the
> server and then use authenticated URLs to access the movie files.
>
> Has anyone done something like this?
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/on-rev-upload-limits-and-Amazon-S3-as-an-alternative-tp3244672p3244672.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>