| Home : Web : SOAP |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 51 - 60 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
|
The first version of the .NET Framework exposed Web services as an alternative to .NET Remoting. This was an experiment with open standards such as XML, HTTP, and SOAP. .NET Web services were widely embraced by the developers that recognized their value (please refer to my previous articles). Version 1.1 of the .NET Framework focused on the optimization of the Web service execution mechanism. However, large chunks of architecture were still missing.
Updated: 05/14/2005
|
|
|
At the present, most software development teams have adapted various development methodologies, such as design pattern programming or object-oriented code frameworks, to facilitate their project creation. Different communication standards, such as SOAP or Web Services are also becoming commonplace among large and small firms as a way for them to expand their interoperability with other businesses or improve transaction processes.
Updated: 05/14/2005
|
|
|
The .NET Framework class library provides four namespaces to support object serialization: System.Runtime.Serialization, System.Runtime.Serialization.Formatters, System.Runtime.Serialization.Formatters.Binary, and System.Runtime.Serialization.Formatters.Soap.
Updated: 05/14/2005
|
|
|
To begin with, I would like to make a few necessary remarks about topics that will be discussed in this article and about the minimal level of knowledge the reader should have. The topics are in the title of article—we will talk about SOAP technology, and will try to explain it as quickly and easily as possible, and, it goes without saying, we will include the usual \"Hello World!\" example to show the reader what it looks like. To my mind, it is always harder to start learning new technology if you have only the official documentation, with huge examples, explaining all the features and advantages, but doesn\'t explain what it looks like.
Updated: 05/14/2005
|
|
|
A web service is one of the greatest technologies developed in Internet world, which can be used to connect businesses and clients in a standardized method using XML (Extensible Markup Language), SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language) and UDDI (Universal Description, Discovery and Integration). XML is used for structuring the data, SOAP is used to transfer the data, WSDL is used for describing the services and UDDI is used to get a list of services available. Web services allows application to communicate with each other without worrying about their hardware systems, operating systems and programming languages.
Updated: 05/14/2005
|
|
|
In my prior articles, I\'ve introduced and discussed various aspects of the JAX Pack, a set of APIs for working with Web services and the underlying supporting protocols. In this article, we\'ll look at JAX-RPC, a specification for making remote procedure calls via XML and SOAP over HTTP. Specifically we\'ll look at the client side of JAX-RPC, as it shows the most promise.
Updated: 05/14/2005
|
|
|
As you begin to move more of your code over onto the Internet via Web Services you will notice that creating the actual server is the simplest part. Take the Microsoft WSDL .SOAP Toolkit Wizard and apply it to your COM, and it creates the necessary files on the server for you. Don\'t you wish you could simply run another wizard and have it create the files for a client just as easily? That\'s what I have done here. I\'ve created a wizard that creates the client files for you, based on the Simple Object Access Protocol (SOAP) Toolkit V2, SP 2.
Updated: 05/14/2005
|
|
|
When we look at the term \"generic\", unrelated to the programming world, it simply means something that is not tied to any sort of brand name. For example, if we purchase some generic dish soap, soap that has no brand name on it, we know that we are buying dish soap and expect it to help us clean our dishes, but we really don\'t know what exact brand (if any) will be inside the bottle itself. We can treat it as dish soap even though we don\'t really have any idea of its exact contents.
Updated: 05/14/2005
|
|
|
Welcome to Part 2 of our journey through the Global XML Web Services Architecture (GXA). In Part 1 we learned that GXA is an application-level protocol framework built on top of XML and SOAP that provides a consistent model for building infrastructure-level protocols for Web services and applications. By doing so, GXA \"fills the gap\" in the current Web services stack. We also learned that GXA specifications can be grouped in seven main \"concentrations,\" as shown below:
Updated: 05/14/2005
|
|
|
In this article, we will see how to use Web services in a real-time Web application. Even though Web services are very powerful and based on open Internet protocols such as XML, HTTP and SOAP (that accounts for platform independence), using them in a real-time Web site requires careful consideration of performance implications. For example, if before showing a particular page you try to call out two or three Web services across the Internet to get data, the responsiveness of the site is going to be severely impacted. At the same time, you cannot avoid calling out to Web services to get the data you want.
Updated: 05/14/2005
|
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 51 - 60 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
