...
To present named object listings as if they were in a traditional file system, SwarmNFS creates a simulation: it translates each forward slash (/) in any object name into a traditional directory delimiter. SwarmNFS then presents a view of objects at the simulated directory level. For example, suppose these named objects exist in the bucket “AcmeBucket”:
| Code Block | ||
|---|---|---|
| ||
/Sales/Leads/campaigns/2016/Jan/list.xls /Sales/Leads/campaigns/2016/Feb/list.xls /Sales/Leads/campaigns/addword.xls /Sales/Leads/campaigns/partners.xls |
| Info | ||
|---|---|---|
| ||
Objects in Swarm Storage use forward slashes in their names for directory delimiting; SwarmNFS converts these to backslashes inline during listing transfers only if a client expects backslashes to be the directory delimiter. SwarmNFS always converts backslashes to forward slashes when communicating with Swarm Storage (including through Gateway). To be valid, object and bucket names must not start with a slash; if you have existing ones so named, they will not appear in SwarmNFS listings. If this occurs, rename and upload them with valid names. |
By default, for a client request for a bucket-level listing, SwarmNFS provides a simulated view of the first level of contents within the bucket:
...