<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2013-05-23T08:02:42Z</responseDate>
  <request identifier="oai:CiteSeerX.psu:10.1.1.42.2177" metadataPrefix="oai_dc" verb="GetRecord">http://citeseerx.ist.psu.edu/oai2</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:CiteSeerX.psu:10.1.1.42.2177</identifier>
        <datestamp>2009-04-12</datestamp>
      </header>
      <metadata>
        <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Adapting to Network and Client Variation Using Active Proxies: Lessons and Perspectives</dc:title>
          <dc:creator>Armando Fox</dc:creator>
          <dc:creator>Steven D. Gribble</dc:creator>
          <dc:creator>Yatin Chawathe</dc:creator>
          <dc:creator> Eric A. Brewer</dc:creator>
          <dc:subject>1.1 Heterogeneity</dc:subject>
          <dc:subject>Thin Clients and</dc:subject>
          <dc:description>luding screen size, color depth, effective bandwidth, processing power, and ability to handle specific data encodings, e.g., GIF, PostScript, or MPEG. As shown in tables 1 and 2, each type of variation often spans orders of magnitude. High-volume devices such as smart phones [12] and smart two-way pagers will soon constitute an increasing fraction of Internet clients, making the variation even more pronounced. These conditions make it difficult for servers to provide a level of service that is appropriate for every client. Application-level adaptation is required to provide a meaningful Internet experience across the range of client capabilities. Although we expect clients to improve over time, there will always be older systems still in use that represent relatively obsolete clients, and the high end will advance roughly in parallel with the low end, effectively maintaining a gap between the two: there will always be a large difference between the very best laptop and t</dc:description>
          <dc:contributor>The Pennsylvania State University CiteSeerX Archives</dc:contributor>
          <dc:publisher/>
          <dc:date>2009-04-12</dc:date>
          <dc:date>2007-11-22</dc:date>
          <dc:date>1998</dc:date>
          <dc:format>application/postscript</dc:format>
          <dc:type>text</dc:type>
          <dc:identifier>http://citeseerx.ist.psu.edu/citeseerx/viewdoc/summary?doi=10.1.1.42.2177</dc:identifier>
          <dc:source>http://www.cs.berkeley.edu/~yatin/papers/adaptation.ps.gz</dc:source>
          <dc:language>en</dc:language>
          <dc:relation>10.1.1.38.1298</dc:relation>
          <dc:relation>10.1.1.12.448</dc:relation>
          <dc:relation>10.1.1.112.9002</dc:relation>
          <dc:relation>10.1.1.21.1584</dc:relation>
          <dc:relation>10.1.1.145.8046</dc:relation>
          <dc:relation>10.1.1.1.2034</dc:relation>
          <dc:relation>10.1.1.32.6145</dc:relation>
          <dc:relation>10.1.1.37.8716</dc:relation>
          <dc:relation>10.1.1.132.6511</dc:relation>
          <dc:relation>10.1.1.112.6464</dc:relation>
          <dc:relation>10.1.1.41.6760</dc:relation>
          <dc:relation>10.1.1.32.7346</dc:relation>
          <dc:relation>10.1.1.41.4993</dc:relation>
          <dc:relation>10.1.1.41.4031</dc:relation>
          <dc:relation>10.1.1.35.8868</dc:relation>
          <dc:relation>10.1.1.39.8564</dc:relation>
          <dc:rights>Metadata may be used without restrictions as long as the oai identifier remains attached to it.</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
