<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for Advansen - Advanced Software Engineering</title>
	<link>http://www.advansen.com</link>
	<description>"The best code only comes from a good design" -- Gabriel Gonzalez 's Weblog</description>
	<pubDate>Mon, 08 Sep 2008 00:08:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>Comment on Modelling a Plugin System by Gabriel Gonzalez</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-289</link>
		<dc:creator>Gabriel Gonzalez</dc:creator>
		<pubDate>Mon, 29 Jan 2007 08:45:23 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-289</guid>
		<description>Ah! Ok mate so you was talking about which functionalities could be extended in the future so you can from them develop the plugin subsystem :)

Maybe you would enjoy a tiny entry I post at &lt;a href="http://www.skyscrapr.net/blogs/solution/archive/2007/01/27/673.aspx" rel="nofollow"&gt;http://www.skyscrapr.net/blogs/solution/archive/2007/01/27/673.aspx&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Ah! Ok mate so you was talking about which functionalities could be extended in the future so you can from them develop the plugin subsystem <img src='http://www.advansen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Maybe you would enjoy a tiny entry I post at <a href="http://www.skyscrapr.net/blogs/solution/archive/2007/01/27/673.aspx" rel="nofollow">http://www.skyscrapr.net/blogs/solution/archive/2007/01/27/673.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Modelling a Plugin System by Alejandro Espinoza</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-288</link>
		<dc:creator>Alejandro Espinoza</dc:creator>
		<pubDate>Mon, 29 Jan 2007 02:23:53 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-288</guid>
		<description>I think you misunderstood me.... but it is ok. Because what you just described is exactly what I had in mind. 

What I meant was that you need to decide what parts can be extensible, for example the Parser mechanism: PDF or DOC. Not extend the PDF mechanism, but the parser mechanism.</description>
		<content:encoded><![CDATA[<p>I think you misunderstood me&#8230;. but it is ok. Because what you just described is exactly what I had in mind. </p>
<p>What I meant was that you need to decide what parts can be extensible, for example the Parser mechanism: PDF or DOC. Not extend the PDF mechanism, but the parser mechanism.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Modelling a Plugin System by Gabriel Gonzalez</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-287</link>
		<dc:creator>Gabriel Gonzalez</dc:creator>
		<pubDate>Sat, 27 Jan 2007 12:28:52 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-287</guid>
		<description>I think I got your point, but I do not agree. After you design and develop the system you shuldn't go to it everytime you need to add a new plug-in system, it should somehow be able to pass message through a well-defined API which will not change.

Of course you can use stratage pattern or whatever you like more for achiving a plug-in system but if you are creating a new plug-in to store documents in PDF format you should just develop the subsystem from the given API e.g. "newDoc()", "title()", "author()", "sign()" and so on.

You should not allow to extend this API since otherwise the point of having a plug-in system is blurred.

If I have not got your point you can turn into spanish and try it again :)</description>
		<content:encoded><![CDATA[<p>I think I got your point, but I do not agree. After you design and develop the system you shuldn&#8217;t go to it everytime you need to add a new plug-in system, it should somehow be able to pass message through a well-defined API which will not change.</p>
<p>Of course you can use stratage pattern or whatever you like more for achiving a plug-in system but if you are creating a new plug-in to store documents in PDF format you should just develop the subsystem from the given API e.g. &#8220;newDoc()&#8221;, &#8220;title()&#8221;, &#8220;author()&#8221;, &#8220;sign()&#8221; and so on.</p>
<p>You should not allow to extend this API since otherwise the point of having a plug-in system is blurred.</p>
<p>If I have not got your point you can turn into spanish and try it again <img src='http://www.advansen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Modelling a Plugin System by Alejandro Espinoza</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-286</link>
		<dc:creator>Alejandro Espinoza</dc:creator>
		<pubDate>Sat, 27 Jan 2007 07:28:47 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-286</guid>
		<description>Yep, I agree documentation sucks, that is why Software Factories seems so interesting...anyways...sorry for not explaining myself correctly, but English is my second language and sometimes I use words that I shouldn't.

What I meant with 'aspects extensibility' I meant: what parts/features of the software are going to be extensible. 

For example let's say you want to make a feature which parses files. You can make the File Parser aspect of the application extensible or interchangeable (maybe following an Strategy pattern).  One plug in for PDF files and another for the DOC files.</description>
		<content:encoded><![CDATA[<p>Yep, I agree documentation sucks, that is why Software Factories seems so interesting&#8230;anyways&#8230;sorry for not explaining myself correctly, but English is my second language and sometimes I use words that I shouldn&#8217;t.</p>
<p>What I meant with &#8216;aspects extensibility&#8217; I meant: what parts/features of the software are going to be extensible. </p>
<p>For example let&#8217;s say you want to make a feature which parses files. You can make the File Parser aspect of the application extensible or interchangeable (maybe following an Strategy pattern).  One plug in for PDF files and another for the DOC files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Modelling a Plugin System by Gabriel Gonzalez</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-284</link>
		<dc:creator>Gabriel Gonzalez</dc:creator>
		<pubDate>Sat, 27 Jan 2007 00:22:22 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-284</guid>
		<description>Hey! Having feedback from community is a very nice feeling :)

I agree with you that software == documentation, and that's not a bad point at all. I just find it a pia, having e.g. 5 documents to describe a whole plug-in system, but it it is just my point of view.

I don't get your point of aspects extensibility, could you explain yourself better? 

Thank's a lot :)</description>
		<content:encoded><![CDATA[<p>Hey! Having feedback from community is a very nice feeling <img src='http://www.advansen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I agree with you that software == documentation, and that&#8217;s not a bad point at all. I just find it a pia, having e.g. 5 documents to describe a whole plug-in system, but it it is just my point of view.</p>
<p>I don&#8217;t get your point of aspects extensibility, could you explain yourself better? </p>
<p>Thank&#8217;s a lot <img src='http://www.advansen.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Modelling a Plugin System by Alejandro Espinoza</title>
		<link>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-238</link>
		<dc:creator>Alejandro Espinoza</dc:creator>
		<pubDate>Fri, 26 Jan 2007 07:56:46 +0000</pubDate>
		<guid>http://www.advansen.com/2006/12/01/modelling-a-plugin-system/#comment-238</guid>
		<description>How about just setting the interfaces for such extensibility. The first thing to do is to define the aspects which are going to be extensible, after that just establish a contract which defines what the system requires from the plug in. 

Most certainly this kind of extensibility has to be established and defined in the analysis and design phase.

Now regarding documentation, that is just the nature of software architecture and development. We need to document what we do. If those subsystems were not developed as plugins, they still have to be documented. So I don't think that is a bad point against plug in architectures, it is just the nature of development.</description>
		<content:encoded><![CDATA[<p>How about just setting the interfaces for such extensibility. The first thing to do is to define the aspects which are going to be extensible, after that just establish a contract which defines what the system requires from the plug in. </p>
<p>Most certainly this kind of extensibility has to be established and defined in the analysis and design phase.</p>
<p>Now regarding documentation, that is just the nature of software architecture and development. We need to document what we do. If those subsystems were not developed as plugins, they still have to be documented. So I don&#8217;t think that is a bad point against plug in architectures, it is just the nature of development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on First Audio Show!! by Gabriel Gonzalez</title>
		<link>http://www.advansen.com/2006/09/29/first-audio-show/#comment-43</link>
		<dc:creator>Gabriel Gonzalez</dc:creator>
		<pubDate>Tue, 07 Nov 2006 12:49:28 +0000</pubDate>
		<guid>http://www.advansen.com/2006/09/29/first-audio-show/#comment-43</guid>
		<description>I really appreciate your comments! That motivates me to produce another worthless version of my show heheh

Cheers Rakel!</description>
		<content:encoded><![CDATA[<p>I really appreciate your comments! That motivates me to produce another worthless version of my show heheh</p>
<p>Cheers Rakel!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on First Audio Show!! by kakel</title>
		<link>http://www.advansen.com/2006/09/29/first-audio-show/#comment-42</link>
		<dc:creator>kakel</dc:creator>
		<pubDate>Mon, 06 Nov 2006 11:53:06 +0000</pubDate>
		<guid>http://www.advansen.com/2006/09/29/first-audio-show/#comment-42</guid>
		<description>Hey,
That was fun, I like it and your english is far way from bad.
I'm sorry I cannot comment anything about the stuff you are saying, my lack
of knowlegde is evident, but I really like the idea of hearing things, a speaking
blog good idea.

the boring next-to-be FrauDoktor</description>
		<content:encoded><![CDATA[<p>Hey,<br />
That was fun, I like it and your english is far way from bad.<br />
I&#8217;m sorry I cannot comment anything about the stuff you are saying, my lack<br />
of knowlegde is evident, but I really like the idea of hearing things, a speaking<br />
blog good idea.</p>
<p>the boring next-to-be FrauDoktor</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on First Audio Show!! by Anonymous</title>
		<link>http://www.advansen.com/2006/09/29/first-audio-show/#comment-40</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 29 Sep 2006 21:24:53 +0000</pubDate>
		<guid>http://www.advansen.com/2006/09/29/first-audio-show/#comment-40</guid>
		<description>You are doing great!

:*</description>
		<content:encoded><![CDATA[<p>You are doing great!</p>
<p>:*</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple but yet powerful Memory Leakage Detection System GALD by novenlay</title>
		<link>http://www.advansen.com/2006/07/18/simple-but-yet-powerful-memory-leakage-detection-system-gald/#comment-23</link>
		<dc:creator>novenlay</dc:creator>
		<pubDate>Thu, 20 Jul 2006 10:32:53 +0000</pubDate>
		<guid>http://www.advansen.com/2006/07/18/simple-but-yet-powerful-memory-leakage-detection-system-gald/#comment-23</guid>
		<description>Hi again gain,

ok, you've got my mail (at least I think you see it as  that your site). So mail me some informations when you want, to keep this on. I've got plenty of time for the next 3 months. I search a windows security project, but I always love to contribute on C unix projects.

By the way, I'm french so I can't understand the reply you've got on 48bits, people seems to think as good as me of this first step.

Cya.</description>
		<content:encoded><![CDATA[<p>Hi again gain,</p>
<p>ok, you&#8217;ve got my mail (at least I think you see it as  that your site). So mail me some informations when you want, to keep this on. I&#8217;ve got plenty of time for the next 3 months. I search a windows security project, but I always love to contribute on C unix projects.</p>
<p>By the way, I&#8217;m french so I can&#8217;t understand the reply you&#8217;ve got on 48bits, people seems to think as good as me of this first step.</p>
<p>Cya.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
