<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>IPHere &#187; Code</title> <atom:link href="https://www.iphere.com/tag/code/feed" rel="self" type="application/rss+xml" /><link>https://www.iphere.com</link> <description>We show your current IP</description> <lastBuildDate>Wed, 03 Aug 2022 14:13:56 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.6.1</generator> <item><title>VMware&#8217;s Lost Source Code: Not A Panic Situation</title><link>https://www.iphere.com/vmwares-lost-source-code-not-a-panic-situation</link> <comments>https://www.iphere.com/vmwares-lost-source-code-not-a-panic-situation#comments</comments> <pubDate>Fri, 27 Apr 2012 20:13:07 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Code]]></category> <category><![CDATA[Lost]]></category> <category><![CDATA[Panic]]></category> <category><![CDATA[Situation]]></category> <category><![CDATA[Source]]></category> <category><![CDATA[VMware's]]></category> <guid
isPermaLink="false">http://www.iphere.com/vmwares-lost-source-code-not-a-panic-situation</guid> <description><![CDATA[VMware lost some of their ESX source code. Queue the sky-is-falling claims. Don&#8217;t worry, there&#8217;s no need to panic. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/vmwares-lost-source-code-not-a-panic-situation/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Juniper Offers OpenFlow Source Code To Developers</title><link>https://www.iphere.com/juniper-offers-openflow-source-code-to-developers</link> <comments>https://www.iphere.com/juniper-offers-openflow-source-code-to-developers#comments</comments> <pubDate>Thu, 27 Oct 2011 20:17:06 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Code]]></category> <category><![CDATA[Developers]]></category> <category><![CDATA[Juniper]]></category> <category><![CDATA[Offers]]></category> <category><![CDATA[OpenFlow]]></category> <category><![CDATA[Source]]></category> <guid
isPermaLink="false">http://www.iphere.com/juniper-offers-openflow-source-code-to-developers</guid> <description><![CDATA[Juniper Networks is jumping on the OpenFlow bandwagon, putting the OpenFlow source code in the Junos SDK. The company says that the OpenFlow application works within the SDK to change the control plane to create more dynamic network programmability for custom applications that run on top of the Junos operating system. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/juniper-offers-openflow-source-code-to-developers/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Code 42: Who Are You?</title><link>https://www.iphere.com/code-42-who-are-you</link> <comments>https://www.iphere.com/code-42-who-are-you#comments</comments> <pubDate>Fri, 04 Feb 2011 16:36:08 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Code]]></category> <guid
isPermaLink="false">http://www.iphere.com/code-42-who-are-you</guid> <description><![CDATA[Although Code 42 Software provides consumer-based backup software for desktops and laptops, its focus from a money-making perspective is providing that same capability to organizations with a software/hardware appliance or services. What is intriguing is that Code 42 is a self-proclaimed &#8220;most expensive&#8221; solution, yet continues to grow rapidly. How can that be? Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/code-42-who-are-you/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>