<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.umiacs.umd.edu/adapt/index.php?action=history&amp;feed=atom&amp;title=Pawn2%3AStorage</id>
	<title>Pawn2:Storage - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.umiacs.umd.edu/adapt/index.php?action=history&amp;feed=atom&amp;title=Pawn2%3AStorage"/>
	<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/adapt/index.php?title=Pawn2:Storage&amp;action=history"/>
	<updated>2026-04-05T17:08:41Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.7</generator>
	<entry>
		<id>https://wiki.umiacs.umd.edu/adapt/index.php?title=Pawn2:Storage&amp;diff=2370&amp;oldid=prev</id>
		<title>Toaster at 19:49, 11 March 2009</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/adapt/index.php?title=Pawn2:Storage&amp;diff=2370&amp;oldid=prev"/>
		<updated>2009-03-11T19:49:38Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Storage engines in PAWN are composed of two parts. First is a general storage connection. This comprises the storage driver, and driver settings. The second part of the engine is the path mapper. The path mapper translates the PAWN-mapped path of an item to a local storage engine location. &lt;br /&gt;
&lt;br /&gt;
* Storage Driver&lt;br /&gt;
** Handles the retrieval and storage of bits supplied by a client.&lt;br /&gt;
** Each driver instance has a set of parameters associated with it (ie, user/pass, etc)&lt;br /&gt;
&lt;br /&gt;
* Storage Mapper&lt;br /&gt;
** A mapping agent supplied by a storage engine to map the PAWN context of a file to a storage driver representation.&lt;br /&gt;
** multiple mappers may be configured for each driver instance.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A typical configuration for PAWN would likely be a single storage engine defined for a domain and a domain-wide storage mapper that creates paths based on templates. A most complex example may be a single engine for a domain, but individual storage mappers for each package template specified.&lt;/div&gt;</summary>
		<author><name>Toaster</name></author>
	</entry>
</feed>