{"id":1398,"date":"2005-03-29T00:00:00","date_gmt":"2005-03-29T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/29\/cisco-readying-xml-device\/"},"modified":"2021-12-30T11:39:18","modified_gmt":"2021-12-30T11:39:18","slug":"cisco-readying-xml-device","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/29\/cisco-readying-xml-device\/","title":{"rendered":"Cisco readying XML device"},"content":{"rendered":"<p>Already a powerhouse in the market for Internet routers, Cisco intends to enter the emerging market for XML networking products this year, according to industry sources.  Under a project dubbed Aeon, Cisco is working on a line of networking devices designed to handle network traffic of XML documents, a field already populated by a number of specialised start-ups.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The first product from the Aeon project, which is being tested with a handful of clients in the financial industry, was expected to be released in April but has been pushed back until June, one industry executive said.  With Aeon, Cisco is expected to compete with a number of smaller companies already in the field that build devices designed to speed up XML or process Web services security protocols.<\/p>\n<p>http:\/\/www.zdnet.com.au\/news\/business\/0,39023166,39186268,00.htm<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1398","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1398"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1398\/revisions"}],"predecessor-version":[{"id":3885,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1398\/revisions\/3885"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}