<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: css persistence, flows, sticky, etc.... in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243989#M3477</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's my interpretation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Persistence:  This setting determines whether or not the CSS will allow persistent HTTP connections.  i.e. will a browser be allowed to maintain a single TCP connection for multiple requests, or will it be required to open an individual TCP connection for each bit of content.  In web-server speak, this is sometimes referred to as "keepalive"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Flows:  A flow is CSS speak for a TCP connection.  Once a flow is established, an FTP connection for example, the CSS will maintain that flow for the duration of the connection.  The CSS will not loadbalance traffic "mid-flow" except under unique circumstances, when a service goes down and remap is configured for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sticky:  The various sticky configurations come in to play when you want to have all connections from a particular client go to a particular service.  This is most often accomplished with cookies, or sticky tables which track a clients' IP addresses.  There is a limit to the size of the IP address table, so cookies scale better for web content.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Oct 2003 19:14:25 GMT</pubDate>
    <dc:creator>d.parks</dc:creator>
    <dc:date>2003-10-20T19:14:25Z</dc:date>
    <item>
      <title>css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243988#M3476</link>
      <description>&lt;P&gt;I am trying to understand the differences and similarities of persistence, flows and sticky. The documentation on this subject is not very helpful.  Can someone out there provide a simple explanation of these three very important concepts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!! &lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2003 19:00:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243988#M3476</guid>
      <dc:creator>d.alves</dc:creator>
      <dc:date>2003-10-20T19:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243989#M3477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's my interpretation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Persistence:  This setting determines whether or not the CSS will allow persistent HTTP connections.  i.e. will a browser be allowed to maintain a single TCP connection for multiple requests, or will it be required to open an individual TCP connection for each bit of content.  In web-server speak, this is sometimes referred to as "keepalive"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Flows:  A flow is CSS speak for a TCP connection.  Once a flow is established, an FTP connection for example, the CSS will maintain that flow for the duration of the connection.  The CSS will not loadbalance traffic "mid-flow" except under unique circumstances, when a service goes down and remap is configured for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sticky:  The various sticky configurations come in to play when you want to have all connections from a particular client go to a particular service.  This is most often accomplished with cookies, or sticky tables which track a clients' IP addresses.  There is a limit to the size of the IP address table, so cookies scale better for web content.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Oct 2003 19:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243989#M3477</guid>
      <dc:creator>d.parks</dc:creator>
      <dc:date>2003-10-20T19:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243990#M3478</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;a bit more in detail regarding persistency.&lt;/P&gt;&lt;P&gt;In HTTP 1.1 there are multiple gets per HTTP-Session so if you use persistency all requests in the HTTP-Session will hit the same server. This denies the possibility to offload content (e.g. JPGs) to a cache. If you do not use persistency you split the HTTP1.1 session in multiple HTTP-Sessions on the CSS.&lt;/P&gt;&lt;P&gt;Hope that helps in regards of persistency.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2003 06:31:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243990#M3478</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2003-10-21T06:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243991#M3479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply. It was very helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2003 14:48:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243991#M3479</guid>
      <dc:creator>d.alves</dc:creator>
      <dc:date>2003-10-29T14:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243992#M3480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This was a big help to me regarding my understanding of persistency.  Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2003 14:50:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243992#M3480</guid>
      <dc:creator>d.alves</dc:creator>
      <dc:date>2003-10-29T14:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: css persistence, flows, sticky, etc....</title>
      <link>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243993#M3481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Davon,&lt;/P&gt;&lt;P&gt;glad to hear that.&lt;/P&gt;&lt;P&gt;Please close this posting so that anyone sees that this issue has a "solution" and if you want to, feel free to rate the postings.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Oct 2003 06:05:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-persistence-flows-sticky-etc/m-p/243993#M3481</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2003-10-30T06:05:16Z</dc:date>
    </item>
  </channel>
</rss>

