说明： 采用php的源码实现，jquery sfbrowser是一个使用php和jquery实现的一个简易的上传下载系统的php源码程序，参看、研究和阅读，提升自我 (Using php source code to achieve The the jquery sfbrowser a php source program using php and jquery to achieve a simple upload and download system , see , study and reading , enhance self-)
Connectors for SFBrowser v2.5.3+
================================
A connector folder should at least have the following files.
sfbrowser/connectors/[type]/config.[type]
sfbrowser/connectors/[type]/init.[type]
sfbrowser/connectors/[type]/sfbrowser.[type]
-----------
config file
-----------
The config file should at least have the following settings:
- path of sfbrowser
- the base upload folder
- the language ISO code
- ASCII preview ammount
- a list of forbidden file extensions
- an error return code (for severe misuse).
The config file is used in both the init file (to parse to sfbrowser js) and in the actual sfbrowser file (which does the actual server side thinking).
---------
init file
---------
The init file must be called in the html documents header in order to write these lines:
As you might have noticed, most of these lines are formed to what is set in the config file. The icons variable is a folder readout from the sfbrowser/icons/ folder.
--------------
sfbrowser file
--------------
The sfbrowser file is the actual connector to the SFBrowser plugin. Mostly it will require some POST variables and a JSON output object.
A POST will always contain a variable "a" that will determine the action to be taken.
For all actions counts: make absolutely sure that the incoming data corresponds with that set in the config file!
- Do not upload forbidden filetypes.
- Only upload, rename, create, view, change and delete within base upload path.
- Rename files, but not the file extension.
- Do not return, force download or preview forbidden filetypes.
Mostly, a POST (or GET in case of force download) will contain the variable "folder" and the variable "file". Check both of these against the base upload folder set in the config. If it's outside, somebody is probably screwing around.
Just to be sure, check the number of _GET, _POST and _FILES variables. A _POST["a"] can only get a certain ammount of each, if these differ, something fishy might be going on.
If suspicious action occurs you can redirect them to the return error code set in the config file in order to block acces or whatever you'd like to do(??haven't really figured out how to go from there, consider it a loose stub??).
A number of the JSON outputs contain file descriptions. In the description of the types of actions the file object is referred to as . It looks like this:
JSON FileObject: {
file: file name
,mime: file extention
,rsize: file size in bytes
,size: file size in kB, MB or whatever
,time: time in Unix Epoch
,date: time in "j-n-Y H:i"
,width: image width in pixels
,height: image height in pixels
}
example folder: {
file:"blue",
mime:"folder",
rsize:0,
size:"-",
time:1229275063,
date:"14-12-2008 18:17"
}
example file: {
file:"readme.txt",
mime:"txt",
rsize:3679,
size:"4kB",
time:1229275065,
date:"14-12-2008 18:17"
}
example image: {
file:"atomen.jpg",
mime:"jpg",
rsize:19005,
size:"19kB",
time:1229275063,
date:"14-12-2008 18:17",
width:254,
height:359
}
The following are the possible values for _POST["a"]: the possible actions that can be taken and the required return values.
_POST["a"]=="fileList" :: retreive file list
requires:
_POST["folder"] path to folder
action:
Read the contents of a folder
Filter out the forbidden file types
If applicable, filter for allowed file types
JSON return: {
error: error message (see lang.js)
,msg: succes message (see lang.js)
,data: