<?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: Delay on PSRIT API in Services Discussions</title>
    <link>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591609#M308</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Omar. Another thing which can greatly improve the utility of the PSIRT API is push notifications.&amp;nbsp; Is there anyway (using API) we could know if a new advisory has been posted ? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Oct 2017 15:09:20 GMT</pubDate>
    <dc:creator>VUPPULURI MEHAR Swarup</dc:creator>
    <dc:date>2017-10-30T15:09:20Z</dc:date>
    <item>
      <title>Delay on PSRIT API</title>
      <link>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591607#M306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are 16 advisories released today, but only we were able to see only 1 for quite a few hours using the PSIRT API. Only recently we started getting all 16 new. What can be the cause?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Oct 2017 18:33:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591607#M306</guid>
      <dc:creator>VUPPULURI MEHAR Swarup</dc:creator>
      <dc:date>2017-10-18T18:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Delay on PSRIT API</title>
      <link>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591608#M307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have engaged the development team and they are looking at the root cause. I will update you once we find out what was the problem. Since it now appears to be corrected, it will be fairly challenging to troubleshoot, but they are looking into it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Oct 2017 22:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591608#M307</guid>
      <dc:creator>Omar Santos</dc:creator>
      <dc:date>2017-10-19T22:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: Delay on PSRIT API</title>
      <link>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591609#M308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Omar. Another thing which can greatly improve the utility of the PSIRT API is push notifications.&amp;nbsp; Is there anyway (using API) we could know if a new advisory has been posted ? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Oct 2017 15:09:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/delay-on-psrit-api/m-p/3591609#M308</guid>
      <dc:creator>VUPPULURI MEHAR Swarup</dc:creator>
      <dc:date>2017-10-30T15:09:20Z</dc:date>
    </item>
  </channel>
</rss>

