Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
our_own_cloud_project
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
die_coolen_jungs
our_own_cloud_project
Commits
6b3df8ae
Commit
6b3df8ae
authored
12 years ago
by
Sam Tuke
Browse files
Options
Downloads
Patches
Plain Diff
Improved class comment block
parent
8744b099
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lib/filesystemview.php
+11
-10
11 additions, 10 deletions
lib/filesystemview.php
with
11 additions
and
10 deletions
lib/filesystemview.php
+
11
−
10
View file @
6b3df8ae
...
...
@@ -22,17 +22,18 @@
/**
* Class to provide app access to files outside of the currently logged in user's data
* folder. Functions are provided to create a "view" into ownCloud's virtual file
* system, and an API similar to the oc_filesystem class is available for manipulating
* those files (including the ability to read, write, and delete files).
* Class to provide access to ownCloud filesystem via a "view", and methods for
* working with files within that view (e.g. read, write, delete, etc.). Each
* view is restricted to a set of directories via a virtual root. The default view
* uses the currently logged in user's data directory as root (parts of
* OC_Filesystem are merely a wrapper for OC_FilesystemView).
*
* Apps that need to access files outside of the user data folders (to modify files
* belonging to a user other than the one currently logged in, for example) should
* use this class directly rather than using OC_Filesystem, or making use of PHP's
* built-in file manipulation functions. This will ensure all hooks and proxies
* are triggered correctly.
*
* Every view can have it's own chroot, giving it access to a part of the
* filesystem and will provide the same functionality as oc_filesystem.
* For instance an app can create a new filesystem view on a data folder belonging
* to a user other than the one logged in, so that it may change the files there
* (use case: enabling sharing of files).
*/
class
OC_FilesystemView
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment