<?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 keepalives in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/keepalives/m-p/76867#M923</link>
    <description>&lt;P&gt;I have a question about failover.  When the CSS detects that a service is failing it goes into a 'dying' status until the keepalive parameters are fullfilled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During the period that a service is dying, if a client who is stuck to the dying service begins to navigate again, what will happen to their request?&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jul 2002 18:32:00 GMT</pubDate>
    <dc:creator>sean.cheney</dc:creator>
    <dc:date>2002-07-15T18:32:00Z</dc:date>
    <item>
      <title>keepalives</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives/m-p/76867#M923</link>
      <description>&lt;P&gt;I have a question about failover.  When the CSS detects that a service is failing it goes into a 'dying' status until the keepalive parameters are fullfilled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During the period that a service is dying, if a client who is stuck to the dying service begins to navigate again, what will happen to their request?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2002 18:32:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives/m-p/76867#M923</guid>
      <dc:creator>sean.cheney</dc:creator>
      <dc:date>2002-07-15T18:32:00Z</dc:date>
    </item>
    <item>
      <title>Re: keepalives</title>
      <link>https://community.cisco.com/t5/application-networking/keepalives/m-p/76868#M924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the connection will have to be reset and a new one will be formed with another available service.&lt;/P&gt;&lt;P&gt;The client will stick to it according to your configuration.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2002 06:30:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/keepalives/m-p/76868#M924</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2002-07-16T06:30:15Z</dc:date>
    </item>
  </channel>
</rss>

