<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Cache Synchronization With Jabber</title>
	<atom:link href="http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/</link>
	<description>Living in a state of accord.</description>
	<pubDate>Thu, 20 Nov 2008 13:56:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-110071</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Mon, 10 Sep 2007 08:44:46 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-110071</guid>
		<description>Oh and I should note, one other big advantage of Jabber is that it handles firewalls really well - assuming of course that the jabber server is on the open internet, you can have all your clients behind firewalls without problems. That's particularly nice if like in our case you have an Australian office that doesn't so much like waiting for light to travel across the pacific and back for every request. You can easily set up a local "mirror" which is actually completely up to date with the main server.</description>
		<content:encoded><![CDATA[<p>Oh and I should note, one other big advantage of Jabber is that it handles firewalls really well - assuming of course that the jabber server is on the open internet, you can have all your clients behind firewalls without problems. That&#8217;s particularly nice if like in our case you have an Australian office that doesn&#8217;t so much like waiting for light to travel across the pacific and back for every request. You can easily set up a local &#8220;mirror&#8221; which is actually completely up to date with the main server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-110059</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Mon, 10 Sep 2007 06:56:15 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-110059</guid>
		<description>@Adrian, thanks, I think I'll play with that idea too. (Because it looks good, easy and cool).</description>
		<content:encoded><![CDATA[<p>@Adrian, thanks, I think I&#8217;ll play with that idea too. (Because it looks good, easy and cool).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109793</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Sat, 08 Sep 2007 21:57:25 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109793</guid>
		<description>Fanck,
JMS is probably a very good solution too, in fact it's probably better - but it's just not as cool. :) We weren't seriously adding this to our product, just experimenting.  Thanks for pointing it out though, I'll keep it in mind if we ever do need to implement something like this.</description>
		<content:encoded><![CDATA[<p>Fanck,<br />
JMS is probably a very good solution too, in fact it&#8217;s probably better - but it&#8217;s just not as cool. :) We weren&#8217;t seriously adding this to our product, just experimenting.  Thanks for pointing it out though, I&#8217;ll keep it in mind if we ever do need to implement something like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109789</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Sat, 08 Sep 2007 21:41:52 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109789</guid>
		<description>Stephan,
We used OpenFire (the opensource version of WildFire), mostly because we're developing a Java webapp and we already have an instance set up internally anyway. I honestly have no idea how well it would scale, I imagine there's a limit there somewhere but if you can keep the messages simple enough and keep it simple to remove things from cache it should scale a long way. For this particular app I imagine we'll need to first split the business and view logic out to it's own server and have the storage layer on a dedicated box (like most database setups are done), we can then have multiple front ends pulling from the one storage box. Later we'll need multiple storage boxes and this synchronization layer. Having separated the storage component out first should mean fewer instances of the storage server and thus less strain on the jabber connections.

Naturally there's a lot of profiling to be done in all this - we were just experimenting with something that seemed cool.</description>
		<content:encoded><![CDATA[<p>Stephan,<br />
We used OpenFire (the opensource version of WildFire), mostly because we&#8217;re developing a Java webapp and we already have an instance set up internally anyway. I honestly have no idea how well it would scale, I imagine there&#8217;s a limit there somewhere but if you can keep the messages simple enough and keep it simple to remove things from cache it should scale a long way. For this particular app I imagine we&#8217;ll need to first split the business and view logic out to it&#8217;s own server and have the storage layer on a dedicated box (like most database setups are done), we can then have multiple front ends pulling from the one storage box. Later we&#8217;ll need multiple storage boxes and this synchronization layer. Having separated the storage component out first should mean fewer instances of the storage server and thus less strain on the jabber connections.</p>
<p>Naturally there&#8217;s a lot of profiling to be done in all this - we were just experimenting with something that seemed cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franck</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109788</link>
		<dc:creator>Franck</dc:creator>
		<pubDate>Sat, 08 Sep 2007 21:37:09 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109788</guid>
		<description>And what about JMS ?

http://www.enterpriseintegrationpatterns.com/ObserverJmsExample.html</description>
		<content:encoded><![CDATA[<p>And what about JMS ?</p>
<p><a href="http://www.enterpriseintegrationpatterns.com/ObserverJmsExample.html" rel="nofollow">http://www.enterpriseintegrationpatterns.com/ObserverJmsExample.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109723</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Sat, 08 Sep 2007 13:05:19 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/09/08/cache-synchronization-with-jabber/#comment-109723</guid>
		<description>Thought about that too some time ago vut didn't carry through. What server do you use? Does it scale to large sites with many cache writes?

Peace
-stephan

-- 
Stephan Schmidt :: stephan@reposita.org
Reposita Open Source - Monitor your software development
http://www.reposita.org 
Blog at http://stephan.reposita.org - No signal. No noise.</description>
		<content:encoded><![CDATA[<p>Thought about that too some time ago vut didn&#8217;t carry through. What server do you use? Does it scale to large sites with many cache writes?</p>
<p>Peace<br />
-stephan</p>
<p>&#8211;<br />
Stephan Schmidt :: <a href="mailto:stephan@reposita.org">stephan@reposita.org</a><br />
Reposita Open Source - Monitor your software development<br />
<a href="http://www.reposita.org" rel="nofollow">http://www.reposita.org</a><br />
Blog at <a href="http://stephan.reposita.org" rel="nofollow">http://stephan.reposita.org</a> - No signal. No noise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
