SOAP 1.1之间的差异，SOAP 1.2是什么，HTTP GET和放大器; HTTP POST方法为Android？ [英] What is the difference between SOAP 1.1, SOAP 1.2, HTTP GET & HTTP POST methods for Android?

问题描述

我工作的一个code为SOAP Web服务，我想知道在SOAP 1.1，SOAP 1.2，HTTP GET和放大器的变化; HTTP POST方法为Android，而这是preferred其中的一种。请网站其使用的URL或者其code的样本。

I am working on a code for SOAP Web services, I would like to know the variations in SOAP 1.1, SOAP 1.2, HTTP GET & HTTP POST methods for Android, and which is the preferred one among them. Please site out a sample of its usage URL or its code.

感谢

推荐答案

在SOAP版本的差异

这两个SOAP版本1.1和SOAP 1.2版是万维网联盟（W3C）的标准。 Web服务可以支持不仅SOAP 1.1，还支持SOAP 1.2进行部署。从SOAP 1.1到SOAP 1.2规范所做的一些变化是显著，而其他的变化是次要的。

Both SOAP Version 1.1 and SOAP Version 1.2 are World Wide Web Consortium (W3C) standards. Web services can be deployed that support not only SOAP 1.1 but also support SOAP 1.2. Some changes from SOAP 1.1 that were made to the SOAP 1.2 specification are significant, while other changes are minor.

在SOAP 1.2规范引入了一些变化SOAP 1.1。此信息不打算成为一个深入的描述，所有SOAP 1.1和SOAP 1.2的新功能和变化。相反，这一信息突出了一些SOAP的当前版本之间的重要区别。

The SOAP 1.2 specification introduces several changes to SOAP 1.1. This information is not intended to be an in-depth description of all the new or changed features for SOAP 1.1 and SOAP 1.2. Instead, this information highlights some of the more important differences between the current versions of SOAP.

更改到SOAP 1.2规范是显著包括以下更新： SOAP 1.1是基于XML 1.0。 SOAP 1.2基于XML信息集（XML信息集）。 设置的XML信息（信息集）提供了一种方式来描述与XSD模式的XML文档。然而，信息集不一定序列使用XML 1.0序列在其上的SOAP 1.1是基于文档。这种新的方式来描述的XML文档有助于揭示其他序列化格式，例如一个二进制协议格式。您可以使用二进制协议的格式压缩的消息成一个紧凑的格式，其中一些详细标注信息可能不是必需的。

The changes to the SOAP 1.2 specification that are significant include the following updates: SOAP 1.1 is based on XML 1.0. SOAP 1.2 is based on XML Information Set (XML Infoset). The XML information set (infoset) provides a way to describe the XML document with XSD schema. However, the infoset does not necessarily serialize the document with XML 1.0 serialization on which SOAP 1.1 is based.. This new way to describe the XML document helps reveal other serialization formats, such as a binary protocol format. You can use the binary protocol format to compact the message into a compact format, where some of the verbose tagging information might not be required.

在SOAP 1.2中，可以使用的结合本说明书到下面的协议，以确定哪个XML序列被用在底层协议数据单元。 HTTP绑定被SOAP 1.2中规定 - 第2部分使用XML 1.0作为SOAP消息信息集的序列化

In SOAP 1.2 , you can use the specification of a binding to an underlying protocol to determine which XML serialization is used in the underlying protocol data units. The HTTP binding that is specified in SOAP 1.2 - Part 2 uses XML 1.0 as the serialization of the SOAP message infoset.

1.2的SOAP提供正式定义的传输协议，比使用HTTP，只要卖方符合被SOAP 1.2中所定义的结合其他框架的能力。而HTTP是无处不在，它是不可靠的，其他的传输包括TCP / IP和MQ。 SOAP 1.2提供SOAP处理模型的去除许多可能导致互操作性的错误在没有的Web服务的互操作性（WS-I）曲线的模糊度的更具体的定义。我们的目标是显著减少使用SOAP 1.2实现不同的供应商之间的互操作性问题的机会。 香皂用于Java（SAAJ）附件API也可以单独作为一个简单的机制来发出SOAP请求。一个重大变化的SAAJ规范是重新present SOAP 1.1的消息和附加的SOAP 1.2格式的消息的能力。例如，SAAJ 1.3版引入了对SOAP头元素一套新的常量和方法是更有利于SOAP 1.2（如getRole（），getRelay（））。也有对工厂进行SAAJ其他方法来创建相应的SOAP 1.1或SOAP 1.2消息。 该XML命名空间的信封和编码模式已经改变了SOAP 1.2。这些变化区分SOAP处理器的SOAP 1.1和SOAP 1.2消息，并支持更改SOAP模式，在不影响现有的实现。 Java体系结构的XML Web服务（JAX-WS）推出同时支持SOAP 1.1和SOAP 1.2的能力。因为JAX-RPC引入的要求来操作的SOAP消息，因为它通过在运行时间遍历，有成为必要重新present该消息在其适当的SOAP上下文。在JAX-WS，许多附加的改进来自于SAAJ 1.3支持的结果。

SOAP 1.2 provides the ability to officially define transport protocols, other than using HTTP, as long as the vendor conforms to the binding framework that is defined in SOAP 1.2. While HTTP is ubiquitous, it is not as reliable as other transports including TCP/IP and MQ. SOAP 1.2 provides a more specific definition of the SOAP processing model that removes many of the ambiguities that might lead to interoperability errors in the absence of the Web Services-Interoperability (WS-I) profiles. The goal is to significantly reduce the chances of interoperability issues between different vendors that use SOAP 1.2 implementations. SOAP with Attachments API for Java (SAAJ) can also stand alone as a simple mechanism to issue SOAP requests. A major change to the SAAJ specification is the ability to represent SOAP 1.1 messages and the additional SOAP 1.2 formatted messages. For example, SAAJ Version 1.3 introduces a new set of constants and methods that are more conducive to SOAP 1.2 (such as getRole(), getRelay()) on SOAP header elements. There are also additional methods on the factories for SAAJ to create appropriate SOAP 1.1 or SOAP 1.2 messages. The XML namespaces for the envelope and encoding schemas have changed for SOAP 1.2. These changes distinguish SOAP processors from SOAP 1.1 and SOAP 1.2 messages and supports changes in the SOAP schema, without affecting existing implementations. Java Architecture for XML Web Services (JAX-WS) introduces the ability to support both SOAP 1.1 and SOAP 1.2. Because JAX-RPC introduced a requirement to manipulate a SOAP message as it traversed through the run time, there became a need to represent this message in its appropriate SOAP context. In JAX-WS, a number of additional enhancements result from the support for SAAJ 1.3.

没有difine POST和GET方法，尤其是Android的....但一​​切都在这里是延异

There is not difine POST AND GET method for particular android....but all here is differance

GET GET方法追加名称/值对的URL，让您检索资源再presentation。这样做的最大的问题是，一个URL的长度是有限的（大约3000字符）导致数据丢失，你应该有你的页面的表单太多的东西，所以这种方法只适用，如果有少量的参数。

GET The GET method appends name/value pairs to the URL, allowing you to retrieve a resource representation. The big issue with this is that the length of a URL is limited (roughly 3000 char) resulting in data loss should you have to much stuff in the form on your page, so this method only works if there is a small number parameters.

这是什么意思我吗？基本上，这使得GET方法毫无价值大多数开发商在大多数情况下。这里是看它的另一种方式：在URL可以截断（并且很可能会得到今天的数据为中心的位点），如果形式使用了大量的参数，或如果参数包含大量数据。此外，在URL上传递的参数是在浏览器的地址栏中可见（YIKES !!!）不显示任何类型的敏感（甚至非敏感）数据的最好的地方，因为你只是乞求好奇的用户惹它。

What does this mean for me? Basically this renders the GET method worthless to most developers in most situations. Here is another way of looking at it: the URL could be truncated (and most likely will be give today's data-centric sites) if the form uses a large number of parameters, or if the parameters contain large amounts of data. Also, parameters passed on the URL are visible in the address field of the browser (YIKES!!!) not the best place for any kind of sensitive (or even non-sensitive) data to be shown because you are just begging the curious user to mess with it.

发表 在替代GET方法是POST方法。此方法包HTTP请求，这使得更清洁URL和强加的形式输出没有大小限制的体内的名称/值对，基本上它是一种没有脑子上使用哪一个。 POST也比较安全，但肯定不会安全。虽然HTTP完全支持CRUD，HTML 4只支持发行通过各种元素GET和POST请求。这种限制已经举行的Web应用程序，从充分利用HTTP回来，并解决它，大多数应用程序超载POST采取一切，但资源的检索服务。

POST The alternative to the GET method is the POST method. This method packages the name/value pairs inside the body of the HTTP request, which makes for a cleaner URL and imposes no size limitations on the forms output, basically its a no-brainer on which one to use. POST is also more secure but certainly not safe. Although HTTP fully supports CRUD, HTML 4 only supports issuing GET and POST requests through its various elements. This limitation has held Web applications back from making full use of HTTP, and to work around it, most applications overload POST to take care of everything but resource retrieval.

<一个href="http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.wsfep.multiplatform.doc%2Finfo%2Fae%2Fae%2Fcwbs_soapverdiffs.html">http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.wsfep.multiplatform.doc%2Finfo%2Fae%2Fae%2Fcwbs_soapverdiffs.html

这篇关于SOAP 1.1之间的差异，SOAP 1.2是什么，HTTP GET和放大器; HTTP POST方法为Android？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！