tag:blogger.com,1999:blog-33768292.post6314529554700697274..comments2010-03-10T09:44:36.838ZJames Pasleyhttp://www.blogger.com/profile/12067199178733230271james.pasley@capeclear.comBlogger2125tag:blogger.com,1999:blog-33768292.post-86408753581849085372007-01-17T02:02:56.555Z2007-01-17T02:02:56.555ZInteresting idea - source routing. Your example is quite restrictive using the same document for all exchanges. Of course, as long as the output document of one service matches the input of another, the document type can change along the way (having intermediate services which just do message format translations would be an option to allow more flexibility in the routing).<br /><br />Although probably not something reference properties were designed for, it is quite a novel use of them. It also begs the question of what, if any, issues this raises about security. If someone can route an approapriate document through multiple servers so easily it could lead to messages being allowed to pass from public to private servers and potentially exposing sensitive services.Hendryhttp://www.blogger.com/profile/13809612313521251016noreply@blogger.comtag:blogger.com,1999:blog-33768292.post-4015222759359855162007-01-11T15:17:18.098Z2007-01-11T15:17:18.098ZThe age old dichotomy of good and evil comes to mind. Is this the dichotomy of orchestration and choreography? But which is the evil and which is the good?? :-)David Blackhttp://radio.weblogs.com/0146416/noreply@blogger.com