<?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: Service Oriented Reuse</title>
	<atom:link href="http://www.udidahan.com/2006/04/22/service-oriented-reuse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2006/04/22/service-oriented-reuse/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Sat, 11 Feb 2012 15:16:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Wood</title>
		<link>http://www.udidahan.com/2006/04/22/service-oriented-reuse/comment-page-1/#comment-293</link>
		<dc:creator>John Wood</dc:creator>
		<pubDate>Thu, 27 Apr 2006 09:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/275#comment-293</guid>
		<description>Although not that common, I find it best to develop re-usable services that have their dependencies passed in almost as parameters (although that&#039;s not the exact model I have used personally). So a good customer validation service would have services passed in that know how to retrieve customer information. This is really the only way to achieve true loose coupling and maximum re-use. So can a service have a database - yes it could, but if there&#039;s clear potential for re-use then it probably shouldn&#039;t.

</description>
		<content:encoded><![CDATA[<p>Although not that common, I find it best to develop re-usable services that have their dependencies passed in almost as parameters (although that&#8217;s not the exact model I have used personally). So a good customer validation service would have services passed in that know how to retrieve customer information. This is really the only way to achieve true loose coupling and maximum re-use. So can a service have a database &#8211; yes it could, but if there&#8217;s clear potential for re-use then it probably shouldn&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udi Dahan - The Software Simplist</title>
		<link>http://www.udidahan.com/2006/04/22/service-oriented-reuse/comment-page-1/#comment-292</link>
		<dc:creator>Udi Dahan - The Software Simplist</dc:creator>
		<pubDate>Thu, 27 Apr 2006 04:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/275#comment-292</guid>
		<description>When you say that a service has no state, do you mean to say that a service could not have its own DB? If so, could you explain why?</description>
		<content:encoded><![CDATA[<p>When you say that a service has no state, do you mean to say that a service could not have its own DB? If so, could you explain why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Wood</title>
		<link>http://www.udidahan.com/2006/04/22/service-oriented-reuse/comment-page-1/#comment-291</link>
		<dc:creator>John Wood</dc:creator>
		<pubDate>Wed, 26 Apr 2006 03:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/275#comment-291</guid>
		<description>&gt;&gt; &quot;Customer service&quot; - the service in charge of everything dealing with customers &lt;&lt;
That sounds like a component not a service. A service has one distinct function and usually has no state. Customer validation would be a service. So why wouldn&#039;t an order processing service be able to use the customer validation service?</description>
		<content:encoded><![CDATA[<p>&gt;&gt; &#8220;Customer service&#8221; &#8211; the service in charge of everything dealing with customers &lt;&lt;<br />
That sounds like a component not a service. A service has one distinct function and usually has no state. Customer validation would be a service. So why wouldn&#8217;t an order processing service be able to use the customer validation service?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

