Blogs by topic Patterns and user cajo
| • Accessibility | • Ajax | • Blogging | • Business | • Community |
| • Databases | • Deployment | • Distributed | • Eclipse | • Education |
| • EJB | • Extreme Programming | • Games | • GlassFish | • Grid |
| • GUI | • IDE | • Instant Messaging | • J2EE | • J2ME |
| • J2SE | • Jakarta | • JavaFX | • JavaOne | • Jini |
| • JSP | • JSR | • JXTA | • LDAP | • Linux |
| • Mobility | • NetBeans | • Open Source | • OpenSolaris | • OSGi |
| • P2P | • Patterns | • Performance | • Porting | • Programming |
| • Research | • RMI | • RSS Feeds | • Search | • Security |
| • Servlets | • Struts | • Swing | • Testing | • Tools |
| • Virtual Machine | • Web Applications | • Web Design | • Web Development Tools | • Web Services and XML |
Patterns
The spirited debate following my last post on messaging being degenerate RPC got me thinking; is there some way to combine these two somewhat orthogonal methodologies, to create a unique hybrid approach? A bit of insight led me back to update the original cajo Queue messaging class, and the results were indeed most satisfying.
As a client, ever need to only use a portion of a service object's interface? How about small pieces from several of its interfaces? It could really simplify things to use a custom interface, containing only the methods needed. This is Dynamic Client Subtyping; let me show you how it's done.
