<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>TuteBox &#187; hanxlk</title> <atom:link href="http://www.tutebox.com/author/hanxlk/feed/" rel="self" type="application/rss+xml" /><link>http://www.tutebox.com</link> <description>&#34;Knowledge belongs to the world, be proud to pass it on&#34; - Tutebox</description> <lastBuildDate>Sun, 05 Sep 2010 08:51:16 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>Design Patterns : Iterator pattern</title><link>http://www.tutebox.com/programming/design-patterns-iterator-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-iterator-pattern/#comments</comments> <pubDate>Wed, 01 Sep 2010 19:10:38 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=2134</guid> <description><![CDATA[What is iteration? In computer science, an iterator is an object which allows a programmer to traverse through all the elements of a collection, regardless of its specific implementation. An iterator is sometimes called a cursor, especially within the context of a database. Intent Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation. Diagram Applicability Use Iterator pattern To access an aggregate object’s contents without exposing its internal [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-iterator-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Builder pattern</title><link>http://www.tutebox.com/programming/design-patterns-builder-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-builder-pattern/#comments</comments> <pubDate>Tue, 31 Aug 2010 14:13:12 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=2127</guid> <description><![CDATA[Motivation To reduce the size of a class that has many methods. Also to allow step-by-step construction of a target object. Intent Separate the construction of complex object from its representation so that the same construction process can create different representations. Diagram Applicability Use Builder pattern when; You want to vary the internal representation of the product it builds. It also hides the details of how the product is assembled. You want to construct the [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-builder-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Facade pattern</title><link>http://www.tutebox.com/programming/design-patterns-facade-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-facade-pattern/#comments</comments> <pubDate>Sat, 28 Aug 2010 05:19:17 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=2066</guid> <description><![CDATA[Motivation Structuring a system in to subsystem helps reduce complexity. A common design goal is to minimize the commutation and dependencies between systems. One way to achieve this goal is to introduce a façade object that provides a single, simplified interface to the more general facilities of a subsystem. Intent Provide a unified interface to a set of interfaces in a Wrapper. Diagram Applicability Use Façade pattern when You want to provide a simple interface [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-facade-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Adapter pattern</title><link>http://www.tutebox.com/programming/design-patterns-adapter-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-adapter-pattern/#comments</comments> <pubDate>Fri, 27 Aug 2010 13:32:28 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=2045</guid> <description><![CDATA[Motivation Sometime a toolkit class that’s designed for reuse isn’t reusable only because its interface doesn’t match the domain-specific interface an application requires. Intent Convert the interface of a class into another interface client expects. Adapter lets classes work together that couldn’t otherwise because of incompatible interfaces. Diagram Applicability You want to use an existing class, and its interface does not match the one you need. You want to create a reusable class that cooperates [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-adapter-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Flyweight pattern</title><link>http://www.tutebox.com/programming/design-patterns-flyweight-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-flyweight-pattern/#comments</comments> <pubDate>Mon, 23 Aug 2010 03:47:30 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1961</guid> <description><![CDATA[Motivation There are cases in programming where it seems that you need to generate a very large number of small class instances to represent data. Sometimes you can greatly reduce the number of different classes that you need to instantiate if you can recognize that the instances are fundamentally the same except for a few parameters. Intent Use sharing to support large numbers of fine-grained objects efficiently. Applicability Use flyweight pattern when An application uses [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-flyweight-pattern/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Design Patterns : Singleton</title><link>http://www.tutebox.com/programming/design-patterns-responsibility-pattern-singleton/</link> <comments>http://www.tutebox.com/programming/design-patterns-responsibility-pattern-singleton/#comments</comments> <pubDate>Wed, 18 Aug 2010 03:57:59 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1943</guid> <description><![CDATA[Motivation It is important for some classes to have exactly one instance. As an example although there can be many printers in a system, there should be only one printer spooler. How do we ensure that a class has only one instance and that the instance is easily accessible within the network? Intent To ensure that a class has only one instance, and to provide a global point of access to it. Regardless of the [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-responsibility-pattern-singleton/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Chain of Responsibility</title><link>http://www.tutebox.com/programming/design-patterns-chain-of-responsibility/</link> <comments>http://www.tutebox.com/programming/design-patterns-chain-of-responsibility/#comments</comments> <pubDate>Mon, 16 Aug 2010 12:46:52 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1905</guid> <description><![CDATA[Motivation Object-oriented developers strive to keep object loosely coupled, keeping the responsibility between objects specific and minimal.. This leads to introduce a change easily with less risk of defects. Clients see only an object’s visible interface and remain isolated from the details of the object’s implementation. &#160; Intent Avoid coupling the sender of a request to its receiver by giving more than one object the chance to handle the request. To apply this pattern, chain [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-chain-of-responsibility/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Observer Pattern</title><link>http://www.tutebox.com/programming/design-patterns-observer-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-observer-pattern/#comments</comments> <pubDate>Sat, 14 Aug 2010 07:42:45 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[programming]]></category> <category><![CDATA[Software Architecture]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1888</guid> <description><![CDATA[Intent Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically. Applicability Use Observer pattern when An abstraction has two aspects, one dependent on the other. Encapsulating these aspects in separate objects let you vary and reuse them independently. A change to one object requires changing others, and you don’t know how many objects need to be changed. An object should be able to [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-observer-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Factory Method</title><link>http://www.tutebox.com/programming/design-patterns-factory-method/</link> <comments>http://www.tutebox.com/programming/design-patterns-factory-method/#comments</comments> <pubDate>Thu, 12 Aug 2010 02:08:02 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[programming]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1873</guid> <description><![CDATA[Motivation As a class developer, you will ordinarily provide class constructors to let users of your class instantiate it. However, a client that needs an object does not or should not know which of several possible classes to instantiate. &#160; Intent Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses. &#160; Applicability Use Factory Method pattern when • In order [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-factory-method/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Design Patterns : Decorator pattern</title><link>http://www.tutebox.com/programming/design-patterns-decorator-pattern/</link> <comments>http://www.tutebox.com/programming/design-patterns-decorator-pattern/#comments</comments> <pubDate>Wed, 11 Aug 2010 14:14:23 +0000</pubDate> <dc:creator>hanxlk</dc:creator> <category><![CDATA[Design Patterns]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Code Help]]></category> <category><![CDATA[design patterns]]></category> <category><![CDATA[programming]]></category> <category><![CDATA[Software Architecture]]></category> <category><![CDATA[Theories]]></category><guid isPermaLink="false">http://www.tutebox.com/?p=1857</guid> <description><![CDATA[Intent Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to sub-classing for extending functionality. [GoF, p175] Client-specified embellishment of a core object recursively wrapping it. &#160; Diagram &#160; Rules of thumb Adapter provides a different interface to its subject. Proxy provides the same interface. but the decorator provides an enhanced interface. [Gof, p216] Adopter changes an object&#8217;s interface, Decorator enhances an objects responsibilities, Decorator is thus more transparent to the client. [...]]]></description> <wfw:commentRss>http://www.tutebox.com/programming/design-patterns-decorator-pattern/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Optimized content served from: www.tutebox.com @ 2010-09-07 00:05:19 -->