[wiki] Updated: IocContainerInternals/TheBasics/CommonPatterns
| Newsgroups | gmane.comp.java.jicarilla.cvs |
|---|---|
| Message-ID | <[email protected]> |
Date: 2004-03-16T18:06:24 Editor: 130.89.169.128 <> Wiki: JicarillaWiki Page: http://lsd.student.utwente.nl/jicarilla/IocContainerInternals_2fTheBasics_2fCommonPatterns no comment Change Log: ------------------------------------------------------------------------------ @@ -119,7 +119,7 @@ A third choice, which is currently a lot less common (but one I like myself :-D) is to support every kind of caching. The only way to feasibly do that without getting a very ugly and cluttered codebase, is to encapsulate the caching choice into a truly seperate concern (which it really seems to be) and create an abstraction for it. Besides containers, resolvers, and factories, we'll need to have a "Cacher" of some kind. It probably needs to sit somewhere between the container and the factory. A typical setup might result in things like -''TODO: image!'' +attachment:container_cache_sequence_diagram.gif == Concept merging == ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click