Child Item

What is the criteria for namespace?

I want to use the drop box instead of S3.
Dropbox is very satisfactory in its function.

But there are some problems.
There's a concurrent write limit per namespace.

If you have a folder structure like below,
Does everyone have a namespace?

Or does it only apply to subfolders?

Or is it just the top-level folders?

.
└── root (user)/
    ├── FirstNamespace/
    │   ├── FirstFirstNamespace
    │   └── FirstSencodNamespace/
    │       └── FirstSecondFirstNamespace
    └── SecondNamespace/
        ├── SecondFirstNamespace
        └── SecondSecondNamespace

Find more posts tagged with

Developers

Comments

Здравко

@subyankee wrote:
...
Does everyone have a namespace?
Or does it only apply to subfolders?
Or is it just the top-level folders?
...

Hi @subyankee,

None of the above.

Let's see a simple example - personal account where you are working alone (without any shared folder, edit links, file requests, third party apps with app's folder, etc.; only possible view only links, eventually). In such a case you have single namespace - your account root (serving as home folder too). Any of the 'extras', just enumerated, adds something like a volume mounted in particular folder. Every such a 'mountpoint' is a root of corresponding namespace (very similar to mounted volumes in corresponding folders on Mac and Linux; I can't think something similar of related to Windows). In team account different namespaces are all home folders, team folders, etc. in addition to those related to personal account.

In a namespace can reside many files and folders, part of the same space. This space can cover all nested folders or up to one or more folder where other namespaces are mounted on, if any.

Hope this sheds some light.

Greg-DB

@subyankee Здравко is correct; normal folders are not by default their own namespaces. Each of the following gets its own namespace:

home/member folder
team space/folder
shared folder
app folder

The following guides may also be helpful: