<?xml version="1.0"?>
<api>
  <query>
    <search>
      <p ns="0" title="Txn-doc" snippet="...Writes are not even guaranteed to be ordered in the traditional semantics, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that recently-written data could survive a crash even though less-recently-&#10;Most file systems perform write caching, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that modified data are not immediately written to the disk. Writes are defe&#10;" size="32818" wordcount="5208" timestamp="2010-04-25T04:27:03Z" />
      <p ns="0" title="Future Vision" snippet="...tive to another subname, and the order of the subnames is essential to the &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of the name, then using ordering is appropriate. This most commonly occurs &#10;...nce set intersections are commutative its order within the grouping has no &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt;, and optimizers; are free to rearrange it.&#10;" size="63273" wordcount="10176" timestamp="2016-08-25T22:00:43Z" />
      <p ns="0" title="V4" snippet="The ordering of two components of a name either has &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt;, or it does not. If the resolution of one component of the name depends on &#10;...blem is that one is using a byte offset to represent a location whose true &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; is not a byte offset but a directory entry, and doing so for a particular f&#10;" size="121053" wordcount="20187" timestamp="2016-08-25T21:59:52Z" />
      <p ns="0" title="X0reiserfs" snippet="... then invoke those operations without caring to understand any more of the &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of an item&#039;s type than that it determines which item specific item operatio&#10;" size="82853" wordcount="13616" timestamp="2010-12-21T11:47:24Z" />
    </search>
  </query>
</api>