1000 is a hard limit imposed by Amazon, not something I control. Nor is it possible to specify a numeric offset – you have to specifically refer to the 1000th object when requesting objects 1001-2000. Adding a 'marker' parameter to the listObjects method would be straightforward: if present, just pass it through to S3 (ensuring it gets included in the signature string, of course).

That said, it'd probably be more convenient to have the method expose "normal" offset/limit parameters, and then it'd be in charge of figuring out how to query for them with 'marker', so that logic doesn't have to be in the application. However, this could potentially be expensive, as every invocation would have to start at the top and scroll down until it found the desired records. I.e., listObjects(…, limit: 50, offset: 1400) would require quering for the first 1000, throwing them away, and then querying for 1001-2000. In most cases it probably doesn't matter, but it's something to consider if the CFC were to adapt the semantics.

Thanks for that. So how do you suggest to scroll via the ListObjects methods? If I know that listObjects method gets the 1000th item, can I then ask for the next 1000th item or do I have to explictlly refer to the 1000th Object and then start from there. Sorry for the details.

Is there any way the 1000 records can be made into a argument, so when using the method you can choose how many records to bring back.

Yes, the 1000-row limit is expected. The S3 service returns a maximum of 1000 record per LIST request. If you want another "page" of records, you have to rerequest the listing and add the 'marker' parameter, which is an objectKey to start after.

I intentionally didn't make the 'listObjects' method automatically go through and build a complete list of every object within a bucket. It just returns the first page. However, I also haven't implemented a way to supply 'marker' to the method if you need a subsequent "page" of record. You can, however use the 'prefix' argument to request a specific objectKey, if you want the metadata about an object.

Thanks for the cfc it is really excellent am still playing with it. One thing I noticed is that the list object only returns a 1000 items. Is that normal? I am using CFMX Ver 7.

Many thanks,

Gaurav

<cffunction name="deleteS3File" access="public" output="false" returntype="void">
<cfargument name="bucket" type="string" required="true" />
<cfargument name="objectKey" type="string" required="true" />

<cfset q = application.as3.listObjects(bucket, ", '?') />
<cfloop query="q">
<cfif listGetAt(q.name, 1, "/") eq objectKey>
<cfset deleteS3FileInternal(bucket, name, 0) />
</cfif>
</cfloop>
</cffunction>

My first thought is to edit your deleteS3File function. First get the list of objects in the bucket. Loop through them looking for a match of listGetAt(name,1,'/') EQ pseudoDir. With each match call deleteS3FileInternal(bucket, name, 0).

Seem resource intensive though. I was just hoping there was a smarter way to do it that I overlooked.

You can't; S3 doesn't have any concept of containment. Every object is a top-level object which may or may not share a common prefix containing slashes with other objects, so you delete a "folder" by individually deleting each object with that "folder" as a prefix in it's object key.

Most S3 managers will use slashes as a delimiter to emulate browsing folders within your S3 bucket, but it's a UI construct, not something that S3 is actually aware of.

Hope that helps.