<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Jabber Software Development Kit</title>
  <link rel="alternate" href="http://developer.cisco.com/web/jabbersdk/blogroll/-/blogs/rss" />
  <subtitle>Jabber Software Development Kit</subtitle>
  <id>http://developer.cisco.com/web/jabbersdk/blogroll/-/blogs/rss</id>
  <updated>2013-05-18T23:40:05Z</updated>
  <dc:date>2013-05-18T23:40:05Z</dc:date>
  <entry>
    <title>Best practices and browser technical limitations</title>
    <link rel="alternate" href="http://developer.cisco.com/web/jabbersdk/blogroll/-/blogs/best-practices-and-browser-technical-limitations" />
    <author>
      <name>Martin Feeney</name>
    </author>
    <id>http://developer.cisco.com/web/jabbersdk/blogroll/-/blogs/best-practices-and-browser-technical-limitations</id>
    <updated>2011-08-04T12:27:00Z</updated>
    <published>2011-08-03T17:34:04Z</published>
    <summary type="html">There are a number of technical limitations imposed by working within a browser sandbox and adapting to its process model. Supporting a wide range of browsers and OSes adds more challenges. In this</summary>
    <dc:creator>Martin Feeney</dc:creator>
    <dc:date>2011-08-03T17:34:04Z</dc:date>
  </entry>
</feed>

