<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>pubsub Release Rss Feed</title><link>http://www.codeplex.com/pubsub/Release/ProjectReleases.aspx</link><description>pubsub Release Rss Description</description><item><title>Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>https://pubsub.codeplex.com/releases/view/98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Sat, 27 Apr 2013 15:23:56 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130427032356P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>
&lt;div class="wikidoc"&gt;
&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000
 production servers across 24 data centers. With this new topology, the goal is to support 100,000&amp;#43; servers.&lt;br&gt;
&lt;br&gt;
I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is
 you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example,
&lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br&gt;
&lt;br&gt;
I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the
&lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br&gt;
&lt;br&gt;
The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section.
 If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br&gt;
&lt;br&gt;
To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Sat, 27 Apr 2013 15:23:56 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130427032356P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>https://pubsub.codeplex.com/releases/view/98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Fri, 19 Apr 2013 17:25:21 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130419052521P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>
&lt;div class="wikidoc"&gt;
&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000
 production servers across 24 data centers. With this new topology, the goal is to support 100,000&amp;#43; servers.&lt;br&gt;
&lt;br&gt;
I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is
 you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example,
&lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br&gt;
&lt;br&gt;
I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the
&lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br&gt;
&lt;br&gt;
The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section.
 If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br&gt;
&lt;br&gt;
To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Fri, 19 Apr 2013 17:25:21 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130419052521P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>https://pubsub.codeplex.com/releases/view/98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Tue, 16 Apr 2013 18:57:09 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130416065709P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>
&lt;div class="wikidoc"&gt;
&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000
 production servers across 24 data centers. With this new topology, the goal is to support 100,000&amp;#43; servers.&lt;br&gt;
&lt;br&gt;
I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is
 you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example,
&lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br&gt;
&lt;br&gt;
I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the
&lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br&gt;
&lt;br&gt;
The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section.
 If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br&gt;
&lt;br&gt;
To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Tue, 16 Apr 2013 18:57:09 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130416065709P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Wed, 27 Mar 2013 21:19:22 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130327091922P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>
&lt;div class="wikidoc"&gt;
&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000
 production servers across 24 data centers. With this new topology, the goal is to support 100,000&amp;#43; servers.&lt;br&gt;
&lt;br&gt;
I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is
 you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example,
&lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br&gt;
&lt;br&gt;
I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the
&lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br&gt;
&lt;br&gt;
The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section.
 If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br&gt;
&lt;br&gt;
To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Wed, 27 Mar 2013 21:19:22 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 3.0 (Mar 27, 2013) 20130327091922P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Mon, 26 Nov 2012 17:23:33 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012) 20121126052333P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012)</title><link>http://pubsub.codeplex.com/releases/view/98304</link><description>
&lt;div class="wikidoc"&gt;
&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000
 production servers across 24 data centers. With this new topology, the goal is to support 100,000&amp;#43; servers.&lt;br&gt;
&lt;br&gt;
I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is
 you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example,
&lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br&gt;
&lt;br&gt;
I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the
&lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br&gt;
&lt;br&gt;
The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section.
 If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br&gt;
&lt;br&gt;
To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Mon, 26 Nov 2012 17:23:33 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012) 20121126052333P</guid></item><item><title>Created Release: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012)</title><link>http://pubsub.codeplex.com/releases?ReleaseId=98304</link><description>&lt;div class="wikidoc"&gt;&lt;h2&gt;Important&lt;/h2&gt;
Wsp 3.0 is &lt;b&gt;NOT&lt;/b&gt; backward compatible with Wsp 2.1.&lt;br /&gt;
&lt;h2&gt;Prerequisites&lt;/h2&gt;
You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;Wsp now uses &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; and &lt;b&gt;.Net 4.0&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;3.0 Enhancements&lt;/h2&gt;
I changed the topology from a hierarchy to peer-to-peer groups. This should provide much greater scalability and more fault-resilience. It also means event routing is more deterministic since the maximum number of hops is four. Today Wsp is installed on &amp;gt;9,000 production servers across 24 data centers. With this new topology, the goal is to support 100,000+ servers.&lt;br /&gt;&lt;br /&gt;I changed the event format to a more standard format of standard headers, custom headers, and body. The two primary values to this format is you can apply event filtering based upon headers without having to deserialize the body itself. The second value is you can use your own serializor for the body (which is your object) which can be more performant than the built-in serializer. As an example, &lt;b&gt;protobuf-net&lt;/b&gt; might be a nice choice which can handle richer data structures and is more performant.&lt;br /&gt;&lt;br /&gt;I implemented an &lt;b&gt;Rx (Reactive Extensions)&lt;/b&gt; interface for Wsp. If you choose to use Rx with Wsp, it means your events can go cross-process and cross-machine using a multicast paradigm. See the &lt;b&gt;WspEventListenTest&lt;/b&gt; and &lt;b&gt;WspEventServiceTest&lt;/b&gt; examples for using Rx.&lt;br /&gt;&lt;br /&gt;The entire config file format has changed. The config file is simplified for large installations and it now has the concept of groups. A machine can be in one of two roles: node or hub. If it&amp;#39;s a hub then it needs to be specified as a hub in its group section. If it&amp;#39;s a node, it will connect to one of the hubs specified in its group section. For fault-resilience, you would want at least 3 hubs per group and they should be able to support ~500 nodes.&lt;br /&gt;&lt;br /&gt;To use the built-in logging feature in Wsp, you need to use the Wsp serializer for your event body so it knows how to deserialize your event.&lt;br /&gt;
&lt;h2&gt;Note&lt;/h2&gt;
I still need to write an installation document. In the meantime, feel free to ask questions.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Mon, 26 Nov 2012 17:16:26 GMT</pubDate><guid isPermaLink="false">Created Release: Distributed Pub Sub Event System Version 3.0 (Nov 26, 2012) 20121126051626P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000+ servers to get file version information of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br /&gt;&lt;br /&gt;Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br /&gt;&lt;br /&gt;Logging now serializes events to JSON format.&lt;br /&gt;&lt;br /&gt;To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br /&gt;&lt;br /&gt;The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br /&gt;&lt;br /&gt;I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Fri, 27 Jul 2012 23:58:35 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20120727115835P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>
&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000&amp;#43; servers to get file version information
 of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br&gt;
&lt;br&gt;
Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br&gt;
&lt;br&gt;
&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center
 has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br&gt;
&lt;br&gt;
Logging now serializes events to JSON format.&lt;br&gt;
&lt;br&gt;
To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br&gt;
&lt;br&gt;
The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br&gt;
&lt;br&gt;
I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config
 file. If someone really needs it sooner, let me know.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Fri, 27 Jul 2012 23:58:35 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20120727115835P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000+ servers to get file version information of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br /&gt;&lt;br /&gt;Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br /&gt;&lt;br /&gt;Logging now serializes events to JSON format.&lt;br /&gt;&lt;br /&gt;To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br /&gt;&lt;br /&gt;The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br /&gt;&lt;br /&gt;I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Fri, 27 Jul 2012 23:57:30 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20120727115730P</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000+ servers to get file version information of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br /&gt;&lt;br /&gt;Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br /&gt;&lt;br /&gt;Logging now serializes events to JSON format.&lt;br /&gt;&lt;br /&gt;To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br /&gt;&lt;br /&gt;The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br /&gt;&lt;br /&gt;I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Tue, 20 Dec 2011 00:39:31 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20111220123931A</guid></item><item><title>Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>
&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000&amp;#43; servers to get file version information
 of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br&gt;
&lt;br&gt;
Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br&gt;
&lt;br&gt;
&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center
 has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br&gt;
&lt;br&gt;
Logging now serializes events to JSON format.&lt;br&gt;
&lt;br&gt;
To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br&gt;
&lt;br&gt;
The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br&gt;
&lt;br&gt;
I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config
 file. If someone really needs it sooner, let me know.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Tue, 20 Dec 2011 00:39:31 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20111220123931A</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000+ servers to get file version information of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br /&gt;&lt;br /&gt;Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br /&gt;&lt;br /&gt;Logging now serializes events to JSON format.&lt;br /&gt;&lt;br /&gt;To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br /&gt;&lt;br /&gt;The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br /&gt;&lt;br /&gt;I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Sat, 17 Dec 2011 01:44:28 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20111217014428A</guid></item><item><title>Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>
&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
&lt;b&gt;Latest Enhancement&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
I added WspCommand to the event system. The main reason is the difficulty to collect real-time system information from servers. As an example, with the Wsp command functionality, it is now feasible to send a command to 8,000&amp;#43; servers to get file version information
 of a specific file and get all responses back and process them within a couple of seconds. When we see performance issues in the eco-system, we can now collect real-time forensics from many or all servers to quickly find the state on the servers.&lt;br&gt;
&lt;br&gt;
Creating commands is extensible. You would use the new CommandRequest and CommandResponse classes. To see an example of how to use the classes, you can look at the WspCommand sample application.&lt;br&gt;
&lt;br&gt;
&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center
 has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br&gt;
&lt;br&gt;
Logging now serializes events to JSON format.&lt;br&gt;
&lt;br&gt;
To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br&gt;
&lt;br&gt;
The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br&gt;
&lt;br&gt;
I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config
 file. If someone really needs it sooner, let me know.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Sat, 17 Dec 2011 01:44:28 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 2.1 (Dec 16, 2011) 20111217014428A</guid></item><item><title>Updated Release: Distributed Pub Sub Event System Version 2.1 (Jul 21, 2010)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You need to install the Microsoft Visual C++ 2010 Redistributable Package. You can find it at:&lt;br /&gt;&lt;blockquote&gt;x64    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;&lt;blockquote&gt;x86    &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555" class="externalLink"&gt;http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br /&gt;&lt;br /&gt;Logging now serializes events to JSON format.&lt;br /&gt;&lt;br /&gt;To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br /&gt;&lt;br /&gt;The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br /&gt;&lt;br /&gt;I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config file. If someone really needs it sooner, let me know.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>keithh</author><pubDate>Fri, 01 Jul 2011 17:02:17 GMT</pubDate><guid isPermaLink="false">Updated Release: Distributed Pub Sub Event System Version 2.1 (Jul 21, 2010) 20110701050217P</guid></item><item><title>Released: Distributed Pub Sub Event System Version 2.1 (Jul 21, 2010)</title><link>http://pubsub.codeplex.com/releases/view/49398</link><description>
&lt;div class="wikidoc"&gt;&lt;b&gt;Prerequisite&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
You need to install the Microsoft Visual C&amp;#43;&amp;#43; 2010 Redistributable Package. You can find it at:&lt;br&gt;
&lt;blockquote&gt;x64 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=14632"&gt;
http://www.microsoft.com/download/en/details.aspx?id=14632&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;x86 &lt;a href="http://www.microsoft.com/download/en/details.aspx?id=5555"&gt;
http://www.microsoft.com/download/en/details.aspx?id=5555&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/blockquote&gt;
&lt;br&gt;
&lt;b&gt;2.1 Enhancements&lt;/b&gt;&lt;br&gt;
&lt;br&gt;
Many enhancements and bug fixes have been made to v2.1. In particular, it scales better and works across the WAN better. You now manage the config file for all machines at the origin server which is the top-most node in the hierarchy. In MSN, each data center
 has one or more parent routers which connect to the origin router. The client servers connect to the same name regardless of data center and the DNS resolves the name to a router in their same data center.&lt;br&gt;
&lt;br&gt;
Logging now serializes events to JSON format.&lt;br&gt;
&lt;br&gt;
To improve WAN communication, you can now specify how many socket connections a server has to its parent.&lt;br&gt;
&lt;br&gt;
The whitepaper below is a out of date but close enough. The overview of the system is still mostly accurate.&lt;br&gt;
&lt;br&gt;
I will add a deployment document in the near future to explain how to deploy and what arguments can be passed to the msi. Essentially, you set up your origin router and then all the other deployments you do will point to the origin router to get their config
 file. If someone really needs it sooner, let me know.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Fri, 01 Jul 2011 17:02:17 GMT</pubDate><guid isPermaLink="false">Released: Distributed Pub Sub Event System Version 2.1 (Jul 21, 2010) 20110701050217P</guid></item></channel></rss>