Thursday, September 12, 2002

Today's Groove Programming Tip: Return HRESULTs from script languages that implement COM interfaces [Paresh Suthar's Radio Weblog] 6:15:41 AM

Jim Allchin wants more consumer oriented Web Services. "When we look out on the landscape, we don't see enough Web sites--and, in particular, customer-facing sites--that have XML Web services interfaces that people can take advantage of," Jim Allchin, Microsoft's senior vice president for Windows, told CNET News.com [via CNET News.com] [Paresh Suthar's Radio Weblog] Maybe if they implemented all of GXA (specs does not equal robust proven implementations) and had it out there in full, we would. Right now, there isn't enough of a robust infrastructure and services for consumer oriented Web Services. 5:37:12 AM

Thanks to Clemens Vasters for clearing up a place of confusion for me on whether COM/Interop marshaling happens for COM+  components in the EnterpriseServices namespace of .NET or ServicedComponents.  It doesn't. This would have been rather inefficient if it did. He says "Replicating a post to the DM dotnet list here. The most common misconception about ServicedComponents is that they require the use of COM/Interop and really everyone has bought into that belief. And it is simply wrong." "The Enterprise Services team went a long and very smart way to separate COM Marshaling from COM Transport when they built System.EnterpriseServices and they've done it in such a smart way that only a few people seem to see that they did it. In fact, ServicedComponents make COM transport (including the LRPC mapping) an alternative way of transport that's deeply integrated with the Remoting infrastructure. However, the difference is that ServicedComponent will bypass the channel architecture and replave that with the COM channel architecture: COM/Interop marshaling does not happen for ServicedComponents." 5:03:33 AM

© Copyright 2002 Sam Gentile.