On Dec 14, 2007 11:38 AM, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > You can do all of those things with the WSO2 Registry .. just stick a > policy in as a resource and attach it to whatever services you want (as > the policy is just a URI). You can change the policies and the services > are automatically affected; its even possible to plug in a dependency > handler that will restart the service if execution information was in the > registry.
Sounds elegantly simple, as one would expect from a "webful" design. I use "webful" because I don't want to start YARD - Yet Another Rest Debate. <grin> This elegant use of URIs serves as yet another reminder that while the world very quickly understood the deep power and rich flexibility offered by a universal format standard -- XML -- it has taken that same world much longer to understand the substantially deeper power and richer flexibility offered by a universal identifier standard -- URI. This despite the fact that TBL said long ago that <http://www.furl.net/item/3421653>: The most fundamental specification of Web architecture, while one of the simpler, is that of the Universal Resource Identifier, or URI. The principle that anything, absolutely anything, "on the Web" should identified distinctly by an otherwise opaque string of characters (A URI and possibly a fragment identifier) is core to the universality. By using URIs as the uniform identifier for any (meta)data a reg/rep may contain and by enabling such URIs to be associated with any service/resource WSO2 is able to offer a simpler, more general, more webful annotation solution. Don't *use* the web -- become the web. -- Nick -- Nick Gall Phone: +1.781.608.5871 AOL IM: Nicholas Gall Yahoo IM: nick_gall_1117 MSN IM: (same as email) Google Talk: (same as email) Email: nick.gall AT-SIGN gmail DOT com Weblog: http://ironick.typepad.com/ironick/ Furl: http://www.furl.net/members/ngall
