<?xml version="1.0" encoding="UTF-8"?>

  <rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
  >

  <channel rdf:about="http://ciscoarticles.com/rss/rss.php">
    <title>WAN Optimization</title>
    <link>http://ciscoarticles.com/rss/rss.php</link>
    <description></description>
    <dc:language>en-us</dc:language>
    <dc:rights>Copyright 2013, </dc:rights>
    <dc:publisher>ahmetalperenemir@gmail.com</dc:publisher>
    <dc:creator>ahmetalperenemir@gmail.com</dc:creator>
    <dc:title>WAN Optimization</dc:title>
    <dc:source>http://ciscoarticles.com/rss/rss.php</dc:source>
    <dc:type>Collection</dc:type>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>4</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://ciscoarticles.com/WAN-Optimization/1887.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/WAN-Optimization/1886.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/WAN-Optimization/1885.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/WAN-Optimization/1884.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/WAN-Optimization/1883.html" />
        
        
        
        
        
        
        
        
        
        
                
      </rdf:Seq>
    </items>
  </channel>
  <item rdf:about="http://ciscoarticles.com/WAN-Optimization/1887.html">
<title>Transparent Accelerators</title>
<link>http://ciscoarticles.com/WAN-Optimization/1887.html</link>
<description>Transparent Accelerators
&lt;a name=&quot;to identify&quot; /&gt;Transparent accelerators use similar 
metrics as nontransparent accelerators to identify peer devices on the other end 
of the network (automatic discovery or static configuration) but do not 
manipulate packet headers for data in flight. This helps to ensure compatibility 
with features that are deployed in the ...</description>
<dc:language>en-us</dc:language>
<dc:title>Transparent Accelerators</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=1887</dc:source>
<dc:rights>Copyright 2013, </dc:rights>
<dc:date>2008-07-29T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/WAN-Optimization/1886.html">
<title>Nontransparent Accelerators</title>
<link>http://ciscoarticles.com/WAN-Optimization/1886.html</link>
<description>Nontransparent Accelerators
&lt;a name=&quot;has been&quot; /&gt;Nontransparent accelerators are designed 
to optimize traffic that has been redirected to it and explicitly forward the 
optimized traffic to a statically defined or dynamically discovered peer through 
an explicit connection to that peer accelerator. In this way, the accelerator 
knows about its peer either through ...</description>
<dc:language>en-us</dc:language>
<dc:title>Nontransparent Accelerators</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=1886</dc:source>
<dc:rights>Copyright 2013, </dc:rights>
<dc:date>2008-07-29T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/WAN-Optimization/1885.html">
<title>Architecture of Accelerator Services</title>
<link>http://ciscoarticles.com/WAN-Optimization/1885.html</link>
<description>Architecture of Accelerator 
Services
&lt;a name=&quot;some posture&quot; /&gt;All accelerator devices (and 
acceleration technology in general) have some posture to services deployed in 
the network. These network services include any action that can be performed 
against network packets and flows, including network visibility, monitoring, 
end-to-end performance analysis, control, prioritization, security, and other ...</description>
<dc:language>en-us</dc:language>
<dc:title>Architecture of Accelerator Services</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=1885</dc:source>
<dc:rights>Copyright 2013, </dc:rights>
<dc:date>2008-07-29T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/WAN-Optimization/1884.html">
<title>Integrating Accelerators into the Network</title>
<link>http://ciscoarticles.com/WAN-Optimization/1884.html</link>
<description>Integrating Accelerators into the 
Network
&lt;a name=&quot;iddle1013&quot; /&gt;&lt;a name=&quot;iddle1432&quot; /&gt;&lt;a name=&quot;iddle1433&quot; /&gt;&lt;a name=&quot;coexist with&quot; /&gt;To understand how accelerators 
coexist with the foundational network technologies for visibility, control, and 
resource alignment, it is also important to understand how accelerators 
integrate into the network. Integrating accelerators includes deploying 
accelerators and delivering to the ...</description>
<dc:language>en-us</dc:language>
<dc:title>Integrating Accelerators into the Network</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=1884</dc:source>
<dc:rights>Copyright 2013, </dc:rights>
<dc:date>2008-07-29T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/WAN-Optimization/1883.html">
<title>TCP Optimization</title>
<link>http://ciscoarticles.com/WAN-Optimization/1883.html</link>
<description>TCP Optimization
&lt;a name=&quot;TCP is&quot; /&gt;TCP is particularly challenged in WAN 
environments due to the connection-oriented, guaranteed-delivery behavior of the 
protocol. Furthermore, TCP generally has only a limited amount of memory 
capacity assigned to each connection, meaning only a small amount of data can be 
in flight at a given time. ...</description>
<dc:language>en-us</dc:language>
<dc:title>TCP Optimization</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=1883</dc:source>
<dc:rights>Copyright 2013, </dc:rights>
<dc:date>2008-07-29T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  
  
  
  
  
  
  
  
  
  
  
</rdf:RDF>
