<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Extenders in OSGi &#8211; what is all the buzz about?</title>
	<atom:link href="http://osgi.mjahn.net/2009/03/04/extenders-in-osgi-what-is-all-the-buzz-about/feed/" rel="self" type="application/rss+xml" />
	<link>http://osgi.mjahn.net/2009/03/04/extenders-in-osgi-what-is-all-the-buzz-about/</link>
	<description>A blog about OSGi, software architecture, componentization and everything else, I consider worth writing about.</description>
	<lastBuildDate>Sun, 05 Sep 2010 21:43:33 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mirko Jahn</title>
		<link>http://osgi.mjahn.net/2009/03/04/extenders-in-osgi-what-is-all-the-buzz-about/comment-page-1/#comment-176</link>
		<dc:creator>Mirko Jahn</dc:creator>
		<pubDate>Sat, 07 Mar 2009 02:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://osgi.mjahn.net/?p=98#comment-176</guid>
		<description>Hi Peter,

thanks for your comment. You&#039;re right the core idea behind an extender is nothing new, like many basic ideas in computer science growing popular these days. If you will, even the Mac OS file system works like an extender with respect to applications installed. The point I was trying to make was that more and more people are using extenders at the moment and even the upcoming version 4.2 of the spec reflects this development as you have to admit.

Concerning the role of an extender you&#039;re right on again. An extender doesn&#039;t replace the white board pattern at all. It can certainly make use of one inside to get things done, but there is no need to. The point I was trying to make is that if you look at best practices in OSGi(hmm I somehow hesitate to say patterns), I think the extender becomes more and more important (besides the WB-pattern). Not that people have just came up with it - no, not at all. It&#039;s because extenders are getting used in more and more high profile projects and therefore people should know what they are dealing with. That&#039;s all. 

Of course, when writing this post I wasn&#039;t just writing it to illustrate the pure facts. I also want my readers to get excited about new stuff and encourage them to try new things out - get inspired! Maybe while doing so, I wasn&#039;t as precise as I should have been, I guess.

I hope you can see, I am with you, but it seems I did a bad job in delivering the message. Again, thanks for the feedback and I hope, I was able to clarify it a bit.

Warm regards,
Mirko
P.S.: sorry for blocking your post so long, but Akismet marked it as spam for some reason.</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>thanks for your comment. You&#8217;re right the core idea behind an extender is nothing new, like many basic ideas in computer science growing popular these days. If you will, even the Mac OS file system works like an extender with respect to applications installed. The point I was trying to make was that more and more people are using extenders at the moment and even the upcoming version 4.2 of the spec reflects this development as you have to admit.</p>
<p>Concerning the role of an extender you&#8217;re right on again. An extender doesn&#8217;t replace the white board pattern at all. It can certainly make use of one inside to get things done, but there is no need to. The point I was trying to make is that if you look at best practices in OSGi(hmm I somehow hesitate to say patterns), I think the extender becomes more and more important (besides the WB-pattern). Not that people have just came up with it &#8211; no, not at all. It&#8217;s because extenders are getting used in more and more high profile projects and therefore people should know what they are dealing with. That&#8217;s all. </p>
<p>Of course, when writing this post I wasn&#8217;t just writing it to illustrate the pure facts. I also want my readers to get excited about new stuff and encourage them to try new things out &#8211; get inspired! Maybe while doing so, I wasn&#8217;t as precise as I should have been, I guess.</p>
<p>I hope you can see, I am with you, but it seems I did a bad job in delivering the message. Again, thanks for the feedback and I hope, I was able to clarify it a bit.</p>
<p>Warm regards,<br />
Mirko<br />
P.S.: sorry for blocking your post so long, but Akismet marked it as spam for some reason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Extenders - an introduction &#171; The OSGi Look</title>
		<link>http://osgi.mjahn.net/2009/03/04/extenders-in-osgi-what-is-all-the-buzz-about/comment-page-1/#comment-175</link>
		<dc:creator>Extenders - an introduction &#171; The OSGi Look</dc:creator>
		<pubDate>Fri, 06 Mar 2009 05:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://osgi.mjahn.net/?p=98#comment-175</guid>
		<description>[...] Read the complete &#8220;Extenders in OSGi&#8221; post on &#8220;All the Small Things&#8221; [...]

[WORDPRESS HASHCASH] The comment&#039;s server IP (66.135.48.191) doesn&#039;t match the comment&#039;s URL host IP () and so is spam.</description>
		<content:encoded><![CDATA[<p>[...] Read the complete &#8220;Extenders in OSGi&#8221; post on &#8220;All the Small Things&#8221; [...]</p>
<p>[WORDPRESS HASHCASH] The comment&#8217;s server IP (66.135.48.191) doesn&#8217;t match the comment&#8217;s URL host IP () and so is spam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kriens</title>
		<link>http://osgi.mjahn.net/2009/03/04/extenders-in-osgi-what-is-all-the-buzz-about/comment-page-1/#comment-174</link>
		<dc:creator>Peter Kriens</dc:creator>
		<pubDate>Wed, 04 Mar 2009 14:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://osgi.mjahn.net/?p=98#comment-174</guid>
		<description>I do not think extenders are new nor is there a dichotomy with the white board pattern. Both models are attempts to decouple and one cannot replace the other. 

The core idea of OSGi is that you can add/remove bundles to achieve the behavior you want. In such a model, you need to decouple bundles from each other because centralized control fails miserably in such a dynamic scenario. Both the whiteboard pattern and the extender have their role.

Kind regards,

        Peter Kriens</description>
		<content:encoded><![CDATA[<p>I do not think extenders are new nor is there a dichotomy with the white board pattern. Both models are attempts to decouple and one cannot replace the other. </p>
<p>The core idea of OSGi is that you can add/remove bundles to achieve the behavior you want. In such a model, you need to decouple bundles from each other because centralized control fails miserably in such a dynamic scenario. Both the whiteboard pattern and the extender have their role.</p>
<p>Kind regards,</p>
<p>        Peter Kriens</p>
]]></content:encoded>
	</item>
</channel>
</rss>
