|
|
Browse by Tags
All Tags » Tech Interop (RSS)
Sorry, but there are no more tags available to filter with.
-
Learn how to use Windows Communication Foundation (WCF) to easily create "RESTful" Web Services in .NET 3.5 that can leverage the simplicity, ubiquity, and scalability of Web programming. http://www.developer.com/net/article.php/3695436 Windows Communication Foundation makes impressive strides ahead in version 3.5 by offering fully integrated support for web programming. The semantics of the programming model along with out-of-the-box configuration defaults make creating and hosting "RESTful" web services very simple. WCF allows service creators to expose services using SOAP and REST, increasing their value by catering to the needs and desires of the service consumers.... Read More...
|
-
On July 10-12, Microsoft hosted the fourth successful WS-* plug-fest with a total of nine web services stacks from seven interop partners (BEA, Higgins, Iona, Oracle, Sun, VeriSign, WSO2/Apache). The scenarios tested included both the submitted web services specifications (previously supported in Microsoftâs .Net Framework 3.0 / 'Indigo' release), and the recent OASIS standards updates (new in Microsoftâs upcoming .Net Framework 3.5 / 'Orcas' release). This was the first event where we also tested some CardSpace scenarios for .NET 3.0 / 3.5 - in particular with VeriSign and the open source Higgins Project. The various interop partners were at different points in their release cycles but it was encouraging to me to see they were consistently able to show improved interoperability with Microsoft products over the course of the three days. There was a strong desire among participants to hold a follow-up event in the fall timeframe to continue to provide more coverage of the new OASIS WS-* spec versions once more interop partners have their implementations ready.... Read More...
|
-
This new whitepaper on MSDN describes two scenarios that exercise selected features of WS-Federation in different ways. An enterprise scenario considers bidding on supply-chain contracts, and a healthcare scenario explores providing access to patient records. The difference in the application of these WS-Federaton features will show the flexibility of the features of the specification. These advanced scenarios highlight complex situations with extensive use of WS-Federation, and in the process provide a good introduction to the WS-Federation spec. http://msdn2.microsoft.com/en-us/library/bb498017.aspx... Read More...
|
-
Here is some benchmark data that should dispel the urban myth that Web Service technology is slow. A recent MSDN whitepaper describes some testing to compare WCF performance against the existing .NET Remoting and WSE 2.0/3.0 technologies, and reached the following conclusion: To summarize the results, WCF is 25%-50% faster than ASP.NET Web Services, and approximately 25% faster than .NET Remoting. Comparison with .NET Enterprise Service is load dependant, as in one case WCF is nearly 100% faster but in another scenario it is nearly 25% slower. For WSE 2.0/3.0 implementations, migrating them to WCF will obviously provide the most significant performance gains of almost 4x. [ MSDN Whitepaper - A Performance Comparison of Windows Communication Foundation (WCF) with Existing Distributed Communication Technologies - http://msdn2.microsoft.com/en-us/library/bb310550.aspx ] Don't let concerns about "slowness" of Web Services technology hold you back - it's simply not true!... Read More...
|
-
I found this great sample on the .NET Framework 3.0 community site showing how to create and use a dynamic proxy using Windows Communication Foundation (WCF). The DynamicProxy allows you to create the dynamic WCF client at runtime by specifying the WSDL URI of the service. The DynamicProxy does not depend on the precompiled proxy or configuration. The DynamicProxy uses the MetadataResolver to download the metadata from the service and WsdlImporter to create the contract and binding at runtime. The dynamic proxy can be used to invoke the operations on the service using reflection. http://wcf.netfx3.com/files/folders/development_tools/entry6148.aspx... Read More...
|
-
Yesterday, Microsoft released the first Community Technology Preview (CTP) of a new range of BizTalk Services. By building on the idea of an Enterprise Service Bus and leveraging Microsoft's Internet-ready Web Service technology in .NET 3.0, this creates an Internet Service Bus (ISB) to combine hosted services "in the cloud" working seamlessly with anyone's existing in-house private Web Services and Enterprise Service Bus (ESB) implementations. The initial CTP service offerings cover hosted versions of technologies that Microsoft has been incubating within Connected Systems Division and the Windows Live Labs for the past year: BizTalk Identity Services - federated identity technologies to help developers manage application identity and access control requirements (Available now) BizTalk Connectivity Services - message routing technologies to help developers securely expose a service from behind a firewall or NAT- think of this as firewall friendly B2B messaging (Available now) BizTalk ServiceBus Services - technologies to help create loosely coupled applications with eventing - think of this as Pub/Sub at Internet scale (Coming soon) BizTalk Workflow Services - Simple templates for cross-organization integration and the orchestration of business processes interacting with multiple services (Coming soon) More details of BizTalk Services can be found at http://labs.biztalk.net/ and technical info on how to start experimenting with this ISB technology is in this blog entry by Dennis Pilarinos. There is also some more background information in these two articles on eWeek. What does this mean for businesses and in particular CIO's? Here are some comments from Burton Group that put the overall value proposition into perspective - basically lower IT costs through use of "packaged infrastructure". "BizTalk Services will decrease the edge node footprint while maintaining application access to valuable infrastructure services," said Chris Haddad, an analyst with Burton Group who was briefed on the new strategy. "BizTalk services will increase reliability, scalability and security of service interactions while minimizing infrastructure investment and operational management overhead," he said. Moreover, "BizTalk Services will eliminate in-house proliferation of infrastructure software while increasing a development team's ability to design and build secure event-driven services," Haddad said.... Read More...
|
-
WSO2 and the authors of the WS-MetadataExchange specification invite you to attend a 3-day Interoperability Workshop covering the Web Services Metadata Exchange specification, to be hosted by WSO2 on April 10-12th, 2007 in Auburn, California (45 minutes northeast of Sacramento, CA). More details are posted on the WS-Builders list: http://tech.groups.yahoo.com/group/WS-Builders/message/149... Read More...
|
-
Here's some reference links to parts of the WCF documentation that anyone interested in interoperability with WCF should find most useful. Web Services Protocols Interoperability Guide http://msdn2.microsoft.com/en-us/library/ms734776.aspx Windows Communication Foundation (WCF) implements a number of Web Services Protocols. Many of these protocols include a number of options and extensibility points left to the discretion of the implementer to implement. This topic provides a list of Web Services Protocols implemented by WCF. Other topics within this section provide implementation details for each protocol supported. Web Services Protocols Supported by System-Provided Interoperability Bindings in WCF http://msdn2.microsoft.com/en-us/library/ms730294.aspx Windows Communication Foundation (WCF) is built to interoperate with Web services that support a set of specifications known as the Web Services specifications. To simplify service configuration for interoperability best practices, WCF introduces three interoperable system-provided bindings: System.ServiceModel.BasicHttpBinding, System.ServiceModel.WsHttpBinding, and System.ServiceModel.WsDualHttpBinding. For metadata publication, there are two interoperable system-provided bindings: mexHttpBinding and mexHttpsBinding. This topic lists specifications that are supported by system-provided interoperable bindings. wsHttpBinding http://msdn2.microsoft.com/en-us/library/ms731299.aspx Defines a secure, reliable, interoperable binding suitable for non-duplex service contracts. The binding implements the following specifications: WS-Reliable Messaging for reliability, and WS-Security for message security and authentication. The transport is HTTP, and message encoding is Text/XML encoding.... Read More...
|
|
|
|