| 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: 31 - 40 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
|
This article is the last in a series examining how one might go about sending binary data as part of a SOAP message. This month we look at BEEP, the Blocks Extensible Exchange Protocol. The primary inventor of BEEP is Marshall Rose, a long-time \"protocol wonk\" within the IETF community. Marshall has authored more than 60 RFC\'s, covering everything from core SNMP details to a DTD for IETF RFCs. Like SOAP 1.2, BEEP is described in a transport-neutral manner and is defined in RFC 3080. The most common transport is TCP, and the TCP mapping is found in RFC 3081.
Updated: 05/14/2005
|
|
|
With the proliferation of XML going back and forth over the wire, we have many advantages as .NET developers. SOAP standards, the ability to make remote procedure calls over HTTP through firewalls, the simplification of and seamless validation of B2B and B2C interchanged data via XML and Schema, ADO.NET with the ability to reference XMLData in either ADO DataSet or XMLDataDocument format, and much more.
Updated: 05/14/2005
|
|
|
Web services are built on the Simple Object Access Protocol (SOAP), a powerful protocol that enables cross-platform distributed computing and that most of the major development tool vendors have implemented. The SOAP specification\'s simple nature is a big reason for its broad acceptance, but its current version doesn\'t address some of the more difficult aspects of distributed computing, such as transaction coordination and security. SOAP\'s simplicity has helped increase its adoption rate, but that also means you must implement things not included in SOAP
Updated: 05/14/2005
|
|
|
This is the second in a series of excerpts from \"Chapter 5: Working with Complex Data Types\" of Java and SOAP. This excerpt covers arrays as return values.So far we\'ve been passing arrays as parameters. Now let\'s use an array as the return value of a service method. We\'ll add a method to our service called getMostActive( ), which returns a String[] that contains the symbols for the most actively traded stocks of the day.
Updated: 05/14/2005
|
|
|
Last month we talked about the reasons for associating attachments with SOAP messages, and we looked at the initial SOAP Messages with Attachments (SwA) note. This month we look at Direct Internet Message Encapsulation (DIME), a binary message format; and we\'ll also look briefly at the WS-Attachments specification, which provides a generic framework for SOAP attachments, and a definition for a DIME-based instantiation of that framework.
Updated: 05/14/2005
|
|
|
You\'ve heard the hype, you\'ve read the literature, and you\'re convinced that web services is the next step. You know SOAP and WSDL, and you\'re ready to build something. It\'s time to take web services to the white board. You don\'t want to go plunging into your first web-services project without a proper design process, right? Enter the Unified Modeling Language, which is the white board notation for object-oriented analysis and design (and much more), offering a natural fit to RPC-style service design.
Updated: 05/14/2005
|
|
|
The evolution of the Simple Object Access Protocol (SOAP) (see http://www.w3.org/TR/SOAP/) has challenged the boundaries of the Internet. SOAP and HTTP enables you to logon to external systems and execute remote function calls. Just imagine, using a Web browser in Melbourne, you can go through the Internet and execute methods on your company\'s mainframe in Seattle. This architecture enables cooperative Web servers to expose their business logic without compromising security.
Updated: 05/14/2005
|
|
|
In my prior columns I\'ve examined specific protocols and pieces of the web services infrastructure, including WSDL, SOAP attachments, and so on. I\'ve picked them up, looked all around, and tried to figure out when and how to use them. More importantly, I\'ve tried to uncover some of the dark corners and trade-offs associated with these technologies. While there\'s certainly room for disagreement about some of the suggestions, I think it\'s clear that there\'s a technical basis behind all the commentary.
Updated: 05/14/2005
|
|
|
This week the XML-Deviant reports on a promising discussion concerning potential convergence between several XML protocol activities.During his recent XML 2000 keynote, Jon Bosak outlined a vision of the future of web services, which was summarized as XML as a core technology UDDI to find the services we need SOAP to perform the simple ones ebXML for the most complex ones . For readers not familiar with the projects Bosak cites, some pointers might be useful.
Updated: 05/14/2005
|
|
|
A form -- whether a sheet of paper or a web page -- represents a structured exchange of data. Web services, as typified by emerging standards like SOAP, WSDL, and UDDI, is an excellent approach to exchanging data in a structured way, although usually the exchange is between machines. Since computers are much better at, well, computing, web services is an important and overdue development in the evolution of the Web. Nevertheless, web services applications exchanging information only between machines isn\'t very interesting: lots of electronically accessible information originates with ordinary human beings.
Updated: 05/14/2005
|
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 31 - 40 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
