<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.mqtt.org/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>MQTT</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/"/>
    <id>http://www.mqtt.org/wiki/</id>
    <updated>2012-02-05T09:13:39-08:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://www.mqtt.org/wiki/feed.php" />
    <entry>
        <title>are_topics_dynamic</title>
        <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/doku.php/are_topics_dynamic?do=revisions&amp;rev=1328052375"/>
        <published>2012-01-31T15:26:15-08:00</published>
        <updated>2012-01-31T15:26:15-08:00</updated>
        <id>http://www.mqtt.org/wiki/doku.php/are_topics_dynamic?do=revisions&amp;rev=1328052375</id>
        <author>
            <name>knolleary</name>
        </author>
        <summary>Topics - are they dynamic?

One of the design principles of MQTT is that it should be “zero-admin” (as far as possible).

Therefore, topics on a broker are always expected to be “dynamic” and to require no administrative setup.

i.e. a client subscribes on topic x without knowing whether it exists; it doesn't, so broker silently creates that topic; and the client receives publications on that topic, should they be sent (which, of course, in a pub/sub world, they may never be).</summary>
    </entry>
    <entry>
        <title>design_principles - added thoughts from Arlen</title>
        <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/doku.php/design_principles?do=revisions&amp;rev=1328002955"/>
        <published>2012-01-31T01:42:35-08:00</published>
        <updated>2012-01-31T01:42:35-08:00</updated>
        <id>http://www.mqtt.org/wiki/doku.php/design_principles?do=revisions&amp;rev=1328002955</id>
        <author>
            <name>andypiper</name>
        </author>
        <summary>Design Principles and Assumptions

MQTT was designed for low-bandwidth, high latency networks in the late 1990s/early 2000s. As a result, the designers made a number of key choices which influenced the way it “looks and feels”.

	*  Simplicity, simplicity, simplicity! Don't add too many “bells and whistles” but provide a solid building block which can easily be integrated into other solutions. Be simple to implement.
	*  Publish/subscribe messaging. Useful for most sensor applications, and enabl…</summary>
    </entry>
    <entry>
        <title>coding_bounties - [Completed]  added lanyrd link</title>
        <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/doku.php/coding_bounties?do=revisions&amp;rev=1327848277"/>
        <published>2012-01-29T06:44:37-08:00</published>
        <updated>2012-01-29T06:44:37-08:00</updated>
        <id>http://www.mqtt.org/wiki/doku.php/coding_bounties?do=revisions&amp;rev=1327848277</id>
        <author>
            <name>andypiper</name>
        </author>
        <summary>Have an idea for an MQTT app but don't have the time, skill or knowledge to create it? or just a cool idea you want to share with the community? add it to the list below.

	*  web-based MQTT graphing - a challenge by Roger Light on the Mosquitto blog
	*  a PyGTK desktop pub/sub testing app similar to the GUI in IA92
	*  a “modern” replacement for IA92
		*  cross-platform... could be Java.
		*  Needs updating to latest MQTT v3.1 with user auth.
		*  could look a lot nicer (running IA92 with platf…</summary>
    </entry>
    <entry>
        <title>start - [Documentation &amp; Reference] </title>
        <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/doku.php/start?do=revisions&amp;rev=1327783400"/>
        <published>2012-01-28T12:43:20-08:00</published>
        <updated>2012-01-28T12:43:20-08:00</updated>
        <id>http://www.mqtt.org/wiki/doku.php/start?do=revisions&amp;rev=1327783400</id>
        <author>
            <name>andypiper</name>
        </author>
        <summary>This is a community resource, intended to bring together documentation, code snippets, and links to good sources of information about:

	*  the MQTT protocol and useful topologies
	*  implementations and programming models
	*  use cases and examples</summary>
    </entry>
    <entry>
        <title>technical_articles - created with initial links to dW articles</title>
        <link rel="alternate" type="text/html" href="http://www.mqtt.org/wiki/doku.php/technical_articles?do=revisions&amp;rev=1327779471"/>
        <published>2012-01-28T11:37:51-08:00</published>
        <updated>2012-01-28T11:37:51-08:00</updated>
        <id>http://www.mqtt.org/wiki/doku.php/technical_articles?do=revisions&amp;rev=1327779471</id>
        <author>
            <name>andypiper</name>
        </author>
        <summary>*  Using the IBM Lotus Expeditor micro broker MQTT client to publish messages on IBM developerWorks
	*  Using MQ Telemetry Transport with WebSphere Business Integration Message Broker on IBM developerWorks</summary>
    </entry>
</feed>

