MediaWiki  master
README File Reference

Go to the source code of this file.

Variables

Some quick notes on the file
repository architecture
Functionality as 
always
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about since access
via the file object can be 
cached
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about since access
via the file object can be
whereas access via the
repository should not be
cached Functions which can act
on any file specified in their
parameters typically find
their place either in the
repository where reference to
repository specific
configuration is or static in
members of File or where no
such configuration is needed
File objects are generated by
a factory function from the
repository The repository thus
has full control over the
behavior of its subsidiary
file 
class
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about since access
via the file object can be
whereas access via the
repository should not be
cached Functions which can act
on any file specified in their
parameters typically find
their place either in the
repository where reference to
repository specific
configuration is or static in
members of File or 
FileRepo
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about 
files
 
Some quick notes on the file
repository architecture
Functionality 
is
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about since access
via the file object can be
whereas access via the
repository should not be
cached Functions which can act
on any file specified in their
parameters typically find
their place either in the
repository where reference to
repository specific
configuration is 
needed
 
Some quick notes on the file
repository architecture
Functionality as driven by
data model *The repository
object stores configuration
information about a file
storage method *The file
object is a process local
cache of information about a
particular file Thus the file
object is the primary public
entry point for obtaining
information about since access
via the file object can be
whereas access via the
repository should not be
cached Functions which can act
on any file specified in their
parameters typically find
their place either in the
repository 
object
 

Variable Documentation

Some quick notes on the file repository architecture Functionality as always

Definition at line 3 of file README.

Some quick notes on the file repository architecture Functionality as driven by data model* The repository object stores configuration information about a file storage method* The file object is a process local cache of information about a particular file Thus the file object is the primary public entry point for obtaining information about since access via the file object can be cached
Some quick notes on the file repository architecture Functionality as driven by data model* The repository object stores configuration information about a file storage method* The file object is a process local cache of information about a particular file Thus the file object is the primary public entry point for obtaining information about since access via the file object can be whereas access via the repository should not be cached Functions which can act on any file specified in their parameters typically find their place either in the repository where reference to repository specific configuration is or static in members of File or where no such configuration is needed File objects are generated by a factory function from the repository The repository thus has full control over the behavior of its subsidiary file class
static

Definition at line 3 of file README.

Some quick notes on the file repository architecture Functionality as driven by data model* The repository object stores configuration information about a file storage method* The file object is a process local cache of information about a particular file Thus the file object is the primary public entry point for obtaining information about since access via the file object can be whereas access via the repository should not be cached Functions which can act on any file specified in their parameters typically find their place either in the repository where reference to repository specific configuration is or static in members of File or FileRepo
static
Some quick notes on the file repository architecture Functionality as driven by data model* The repository object stores configuration information about a file storage method* The file object is a process local cache of information about a particular file Thus the file object is the primary public entry point for obtaining information about since access via the file object can be whereas access via the repository should not be cached Functions which can act on any file specified in their parameters typically find their place either in the repository where reference to repository specific configuration is needed
Some quick notes on the file repository architecture Functionality as driven by data model* The repository object stores configuration information about a file storage method* The file object is a process local cache of information about a particular file Thus the file object is the primary public entry point for obtaining information about since access via the file object can be whereas access via the repository should not be cached Functions which can act on any file specified in their parameters typically find their place either in the repository object

Definition at line 3 of file README.