listObjects with Namespace interface

Hi Jason,

AFAIK, you cannot get a path based on an object id (i.e. you can get an object by path but you can't get a path by object).

If your app stores its objects in a standard location, you could construct the path based on your application logic and then get the object.

Thanks,

Aashish

Jason,

ListObjects is an object interface method that will list objects based on listable tag.

The object interface has no notion of paths or other file system semantics.  If your app needs such funtionality consider using the namespace interface.

You can list directories with the namespace interface.

Raj

My data is structure in a namepace-like way, but it has metadata assiciated with it that I'd like to store as tags / listable tags.  I guess listable tags aren't designed to be used with namespace.  (Listable tags can be stored, but not listed in a namespace context.)

Jason Thornbrugh
Principal Solutions Engineer
GSC Demo Cloud

Jason,

You can use listable tags with the namespace interface.

What are you trying to do with tags and namespace objects?

Raj

I'm storing file objects on Atmos in a custom file sharing application.  The directory names and filenames are arbitrarily defined by users submitting content.  Submitted content can only be seen by users once it has been approved by an administrator.

\projectroot\fileset1\files*

\projectroot\fileset2\files*

\projectroot\fileset3\files*

...

I wanted to use a listable attribute called "publish" to determine which data would be available for download in the webapp.

I was thinking of calling listObjects() and chaining it to getSystemMetadata and getShareableUrl():

listObjects("publish") --> getSystemMetadata() --> getShareableUrl()

However, since the full path name of an object cannot be retrieved, I can't do this directly.  Some alternatives are:

1) Store the full pathname of the object as User Metadata at creation time.

2) Enforce a specific data structure whereby the pathname can be guessed correctly.

3) Store an index of published files/directories external to Atmos Storage

Jason Thornbrugh
Principal Solutions Engineer
GSC Demo Cloud

>>The directory names and filenames are arbitrarily defined by users  submitting content.

Just curious - Is the directory path determined by your app, or do users enter the directory path?

Thanks,

Aashish

The path is determined by the user.  The user uploads the data into an FTP cache.  The user then goes into the WebApp and selects a root level directory to push to Atmos.  The directory is processed (zipped, encrypted, and sha1 hashes generated) and then uploaded to Atmos.  On success, the directory and files are purged from the FTP cache.  I actually have enough control of the data that I should be able to use an educated guess to determine the path of the file in this situation.  I was just hoping that Atmos would do the work for me.  :-)

Here's what the files will look like in Atmos.  The words "red", "blue" and "green" are examples of user provided directory names.  The "publish" attribute would be applied to the directory names (red, blue, green).

/app_root/red/red.7z.001

/app_root/red/red.7z.002

/app_root/red/red.7z.003

...

/app_root/blue/blue.7z.001

/app_root/blue/blue.7z.002

/app_root/blue/blue.7z.003

...

/app_root/green/green.7z.001

/app_root/green/green.7z.002

/app_root/green/green.7z.003

...

Jason Thornbrugh
Principal Solutions Engineer
GSC Demo Cloud

Yes, that should work fine.  I appreciate the input.

Jason Thornbrugh
Principal Solutions Engineer
GSC Demo Cloud