Comments on: XMLFrag SOAP header http://stage.vambenepe.com/archives/114 IT management in a changing IT world Tue, 09 Mar 2010 22:10:17 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: William Vambenepe’s blog » Blog Archive » REST in practice for IT and Cloud management (part 2: configuration management) http://stage.vambenepe.com/archives/114#comment-80932 William Vambenepe’s blog » Blog Archive » REST in practice for IT and Cloud management (part 2: configuration management) Fri, 31 Jul 2009 21:09:55 +0000 http://stage.vambenepe.com/archives/114#comment-80932 [...] effect. BTW, I have issues with the details of how these mechanisms work (and I have described an alternative under the motto “if you are going to suffer with WS-Addressing, at least get some value out [...] [...] effect. BTW, I have issues with the details of how these mechanisms work (and I have described an alternative under the motto “if you are going to suffer with WS-Addressing, at least get some value out [...]

]]> By: William Vambenepe’s blog » Blog Archive » WS Resource Access at W3C: the good, the bad and the ugly http://stage.vambenepe.com/archives/114#comment-46744 William Vambenepe’s blog » Blog Archive » WS Resource Access at W3C: the good, the bad and the ugly Thu, 10 Jul 2008 07:59:57 +0000 http://stage.vambenepe.com/archives/114#comment-46744 [...] The resource access part might be worth doing (one more time), but probably not in the same group as things like metadata discovery, message filtering and message chunking, which are not specific to “resource access” situations. And if someone is going to do this again, rather than repeating the not too useful approaches of the past, it may be good to consider alternatives. [...] [...] The resource access part might be worth doing (one more time), but probably not in the same group as things like metadata discovery, message filtering and message chunking, which are not specific to “resource access” situations. And if someone is going to do this again, rather than repeating the not too useful approaches of the past, it may be good to consider alternatives. [...]

]]> By: William Vambenepe’s blog » Blog Archive » WS-ManagementHammer: don’t do it but if you are going to do it anyway then… http://stage.vambenepe.com/archives/114#comment-41831 William Vambenepe’s blog » Blog Archive » WS-ManagementHammer: don’t do it but if you are going to do it anyway then… Thu, 15 May 2008 17:04:45 +0000 http://stage.vambenepe.com/archives/114#comment-41831 [...] Call it SOAPy mashup if you want to feel like you are part of the cool kids. I described such a mechanism a while ago. In effect, it is an improvement on wsman:Selector that an eventual new iteration of [...] [...] Call it SOAPy mashup if you want to feel like you are part of the cool kids. I described such a mechanism a while ago. In effect, it is an improvement on wsman:Selector that an eventual new iteration of [...]

]]> By: log.illsley.org http://stage.vambenepe.com/archives/114#comment-7175 log.illsley.org Sun, 03 Jun 2007 22:16:20 +0000 http://stage.vambenepe.com/archives/114#comment-7175 <strong>WS-SubversiveAddressing...</strong> William Vambenepe published his XMLFrag header proposal earlier this week and it immediately caught my eye. This was in part because of the idea of a ‘WS-SubversiveAddressing’ specification (WS-Addressing has been a lot of my day job at IBM... WS-SubversiveAddressing…

William Vambenepe published his XMLFrag header proposal earlier this week and it immediately caught my eye. This was in part because of the idea of a ‘WS-SubversiveAddressing’ specification (WS-Addressing has been a lot of my day job at IBM…

]]>