|
|
|
 |
|
|
 |
|
 |
 |
|
|
 |
|
|
|
|
| | |
Linking a path can be done in two ways, one of which is much simpler.
Let's say you are a hosted site ('www.mysite.com'), and you wish to link your archive. The following URL would do it nice and easily:
http://www.edgefiles.com/browsedir.x?id=/mysite.com/www
Simple as that, linking to a specific subdirectory is merely appending the specific path onto the URL.
The remaining alternative is to link using the id of the path, this can be seen when browsing the archive.
This results in a smaller URL, but has no real advantage.
| |
Linking a file is almost no different from linking a path.
Using the above example, we'll continue with you wanting to link to the file 'example.zip' found in a few directories deeper.
http://www.edgefiles.com/file.x?id=/mysite.com/www/mydirectory/example.zip
Unfortunately, this results in a rather long URL - not that it creates a problem in any way. It does however make it easy to develop a script based around simply appending the URL onto the base path (http://www.edgefiles.com/file.x?id=).
Once again, using the files' specific ID can achieve the same result - however, hardcoding links as such may not have the end desired effect if files are constantly being added/removed.
We will have a system to allow listing new/popular files from any site in the near future. Including a much more configurable interface for use on hosted sites to allow their users to browse the archive without ever leaving their site!
| |
|
|
|
|
|
|
|
