| 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: 41 - 50 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
|
In most web services presentations, the speaker has a slide of a mobile phone, a PDA, a computer, and other devices communicating with a web service via SOAP and HTTP. You quickly envision a utopia of universal access but overlook the fact that your old Nokia doesn\'t do XML web services. If you have a J2ME-enabled phone connected to the Internet, it\'s very possible to interact with web services directly. However, the majority of mobile phone users do not have these phones, which means an alternative mode of access must be provided.
Updated: 05/14/2005
|
|
|
In my last article I covered the changes from version 7 to version 8 of the draft AtomAPI. Now the latest version of the AtomAPI is version 9 which adds support for SOAP. This change, and its impact on API implementers, will be covered in a future article. In this article I\'m going to build a simple implementation of the AtomAPI.
Updated: 05/14/2005
|
|
|
XML is often used for structured documents like XHTML, rendering or transformation languages like XSLT and XSLFO, and as the basis for extensible network protocols like SOAP. A less well known example of the use of XML in network protocol design is Composite Capabilities/Preference Profiles (CC/PP). The potential impact of CC/PP on the next generation of the Web is substantial. One important characteristic of the next generation Web is the proliferation of types of client access device, often by the same user.
Updated: 05/14/2005
|
|
|
Despite the lack of vendor support, Representational State Transfer (REST) web services have won the hearts of many working developers. For example, Amazon\'s web services have both SOAP and REST interfaces, and 85% of the usage is on the REST interface. Compared with other styles of web services, REST is easy to implement and has many highly desirable architectural properties: scalability, performance, security, reliability, and extensibility.
Updated: 05/14/2005
|
|
|
The XML-Deviant this week takes a brief look back over the REST debate, to see what\'s been learned, and what\'s still to be done. Let a Thousand Threads Bloom The so-called REST versus SOAP discussion looks like it\'s going to be a serious contender for this year\'s \"Debate that Spawned a Thousand Threads\" award. The fact that this web architecture debate has migrated across so many forums is a testament to both the tenacity of the two camps and to the popularity of the Google SOAP API which has reignited the discussion.
Updated: 05/14/2005
|
|
|
This article discusses: The importance of Web services metrics Why you need to measure on the client Writing a metrics measuring app in C# Analyzing the results This article uses the following technologies: SOAP, Web Services, C#, SQL, MSMQ Code download available at: TransactionMetrics.exe (155KB) he success or failure of IT departments can depend on their ability to deliver a high throughput of requests to the services they support. This is especially important for Web services. In order to ensure adequate throughput, you really need to be able to measure response times.
Updated: 05/14/2005
|
|
|
.NET Remoting provides a powerful and high performance way of working with remote objects. Architecturally, .NET Remote objects are a perfect fit for accessing resources across the network without the overhead posed by SOAP based WebServices. .NET Remoting is easier to use than Java\'s RMI, but definately more difficult than creating a WebService.
Updated: 05/14/2005
|
|
|
.NET Remoting provides a powerful and high performance way of working with remote objects. Architecturally, .NET Remote objects are a perfect fit for accessing resources across the network without the overhead posed by SOAP based WebServices. .NET Remoting is easier to use than Java\'s RMI, but definately more difficult than creating a WebService. In this article, we will create a remote object that will return rows from a database table. For the sake of simplicity i have used the NorthWind database that is packed with the installation of the Microsoft SQL Server.
Updated: 05/14/2005
|
|
|
.NET Remoting provides a powerful and high performance way of working with remote objects. Architecturally, .NET Remote objects are a perfect fit for accessing resources across the network without the overhead posed by SOAP based WebServices. .NET Remoting is easier to use than Java\'s RMI, but definately more difficult than creating a WebService. In this article, we will create a remote object, and access this object using the Interface. The object returns rows from a database table. For the sake of simplicity i have used the NorthWind database that is packed with the installation of the Microsoft SQL Server.
Updated: 05/14/2005
|
|
|
Web services vendors will tell you a story if you let them. \"Web services are a cinch,\" they\'ll say. \"Just write the same code you always do, and then press this button; presto, it\'s now a web service, deployed to the application server, with SOAP serializers, and a WSDL descriptor all written out.\" They\'ll tell you a lot of things, but probably most glorious among them will be the claim that you can develop web services effectively without hand-editing SOAP or WSDL. Does this sound too good to be true? Perhaps the case can be made that in some cases SOAP has been relegated to the role of RPC encoding, that it\'s no more relevant to the application developer than IIOP or the DCOM transport.
Updated: 05/14/2005
|
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 41 - 50 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
