Shayton Equilibrium Kitchen Utensil 2003 User Manual
Using MediaScript 17
•
•
•
•
•
HTTP Support Using the FSNet Plug-in
The FSNet plug-in can implement HTTP and FTP access via standard URLs by defining
virtual filesystems named “http” and “ftp”.
virtual filesystems named “http” and “ftp”.
F S N e t a n d M e d i a R i c h V i r t u a l F i l e s y s t e m s
MediaRich accesses files by defining a number of virtual filesystems. A virtual file system
indicates the root of a file tree located somewhere on either the local filesystem or on the
network. When referencing a file via a virtual file path, the virtual filesystem on which the
file is located is specified by prepending the virtual filesystem name followed by a colon
onto the path to that file.
indicates the root of a file tree located somewhere on either the local filesystem or on the
network. When referencing a file via a virtual file path, the virtual filesystem on which the
file is located is specified by prepending the virtual filesystem name followed by a colon
onto the path to that file.
The FSNet plug-in can implement HTTP and FTP access via standard URLs by defining
virtual filesystems named “http” and “ftp”. Since normal HTTP and FTP URLs consist of
these names followed by a colon and then followed by a file path, normal HTTP and FTP
URLs are valid MediaRich virtual file paths.
virtual filesystems named “http” and “ftp”. Since normal HTTP and FTP URLs consist of
these names followed by a colon and then followed by a file path, normal HTTP and FTP
URLs are valid MediaRich virtual file paths.
In addition to the default “http” and “ftp” filesystems, it is possible to set up other
filesystems that refer to resources on HTTP and FTP servers. These URLs would look the
same as the standard URLs except that the “http” or “ftp” keys at the beginning of the
URLs would be some other name to specify that an alternate filesystem is being accessed.
For more information about defining additional HTTP and FTP filesystem, see “Defining
Additional FSNet Virtual Filesystems” on page 19.
filesystems that refer to resources on HTTP and FTP servers. These URLs would look the
same as the standard URLs except that the “http” or “ftp” keys at the beginning of the
URLs would be some other name to specify that an alternate filesystem is being accessed.
For more information about defining additional HTTP and FTP filesystem, see “Defining
Additional FSNet Virtual Filesystems” on page 19.
E n a b l i n g S t a n d a r d H T T P a n d F T P U R L A c c e s s
To allow standard HTTP URLs to be passed to MediaRich as file paths, add the following
line to MediaRich's local.properties file:
line to MediaRich's local.properties file:
filesystem.fsnet.http.Specifier=http
To allow standard FTP URLs to be passed to MediaRich as file paths, add the following line
to the local.properties file:
to the local.properties file:
filesystem.fsnet.ftp.Specifier=ftp
filesystem.fsnet.ftp.Ftp=1
H T T P a n d F T P U R L s
There are a number of MediaScript methods, such as the Media object's load() and
save()
save()
methods, that accept file paths as parameters. The paths passed via these
parameters will often be paths to files on the local filesystem, but can also refer to resources
on a network via the HTTP and FTP protocols.
on a network via the HTTP and FTP protocols.
By enabling standard HTTP and FTP URLs as described in the previous section, references
to files on HTTP and FTP servers take the same form as standard URLs used to access those
files via a web browser. All of the information normally encoded in HTTP and FTP URLs
can be passed to MediaRich. MediaRich will use the supplied information to connect to the
specified network resource.
to files on HTTP and FTP servers take the same form as standard URLs used to access those
files via a web browser. All of the information normally encoded in HTTP and FTP URLs
can be passed to MediaRich. MediaRich will use the supplied information to connect to the
specified network resource.