blocks|key|56472|text|通过SOAP+web服务本身公开CRUD操作本身并没有错。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|56473|很明显，你会发现有很多这样的服务的例子。|56474|但是，根据您的特定需求，您可能会发现使用SOAP的开销太大，或者使用JSON/AJAX等会更好。|56475|因此，我相信，除非你提供关于你的具体细节的更多细节，否则你的问题没有好的答案。|56476|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

There is nothing wrong with exposing the CRUD operations via SOAP web-services per se.

You will obviously find quite a lot of examples for such services.

However depending on your particular requirements you might find that for you using SOAP is too much overhead or that you could be better off using use JSON/AJAX etc.

So I believe that unless you will provide additional details about your particular details there is no good answer for your question.

blocks|key|56509|text|我认为发布一个向匿名的公共“用户”公开CRUD操作的SOAP服务是一个特别糟糕的主意。但是，如果您可以限制这些警告中的一个或两个，那么我认为这没有什么错(而且我已经多次实现了这样的服务)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|56510|56511|除了执行操作所需的任何方法参数外，您还可以要求用户名和密码参数，这些参数实际上是在处理请求之前验证发起者的身份:身份验证失败可以通过返回SOAP异常来通知。如果您特别偏执，您可以选择在SSL|unordered-list-item|56512|上运行该服务。您可以使用服务器解决方案来处理发送和接收请求的问题，该服务器解决方案基于IP进行过滤，允许来自一系列已批准地址的请求。|56513|56514|是的，通过SOAP运行请求是有开销的(与公开直接数据库访问相反)-即将请求包装到HTTP请求中，打开套接字并发送它的处理时间(以及在接收端进行反向操作，然后再次发送响应)-但是，它确实有优势。|56515|Java+(通过Web+)和.Net+(通过VS)都支持将NetBeans服务消费到项目/解决方案中-这样做的最大好处是远程服务上的对象/结构会自动转换为消费应用程序中的本机对象，这非常方便。|56516|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I think publishing a SOAP service that exposes CRUD operations to anonymous, public "users" would be a particularly bad idea. If, however, you can restrict one or both of these caveats, then I see nothing wrong with it (moreover I've implemented such services many times).

<ul>
<li>You can require, in addition to whatever method parameters your require to perform the operation, username &amp; password parameters that in effect authenticates the originator prior to processing the request: a failure to authenticate can be signalled with the return of a SOAP exception. If you were especially paranoid, you could optionally run the service over SSL</li>
<li>You can have the server solution that deals with sending and receiving the requests filter based on IP, onyl allowing requests from a list of approved addresses.</li>
</ul>

Yes, there are overheads to running requests over SOAP (as opposed to exposing direct database access) - namely the processing time to wrap a request into a HTTP request, open a socket &amp; send it (and the reverse at the receiving end and the again for the response) - but, it does have advantages.

Java (though the NetBeans IDE) and .Net (through VS), both support consumption of Web Services into projects / solutions - the biggest benefit of this is that objects / structures on the remote service are automatically translated into native objects in the consuming application, which is exceptionally handy.

blocks|key|2757281|text|如果你想做的只是在web上进行CRUD，那么我将研究一些不同的技术来代替使用WS*来进行REST。SQL+Data+Services+(以前的Project+Astoria)实际上可能是一个很好的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2757282|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/sql/dataservices/default.mspx^0|1D|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If all you want to do is CRUD over the web, I'd look at some different technologies for doing REST instead of using WS*. <a href="http://www.microsoft.com/sql/dataservices/default.mspx" rel="nofollow noreferrer">SQL Data Services</a> (formerly Project Astoria) might actually be a good alternative.

blocks|key|58186|text|如果您想以RESTful方式使用SOAP，那么有一个有趣的标准，WS-Transfer；它提供了松散耦合的CRUD端点；您可以通过它检查消息并相应地操作您的实体。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|58187|然后，您可以在其上分层任何其他内容，如WS-Secure、WS-Reliable+messaging等等。|58188|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Submission/WS-Transfer/^0|W|B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

If you want to use SOAP in a RESTful manner then there is a interesting standard for this, <a href="http://www.w3.org/Submission/WS-Transfer/" rel="nofollow noreferrer">WS-Transfer</a>; which provides loosely coupled CRUD endpoints; from which you inspect the message and act upon your entities accordingly.

Then you can layer whatever else you want on top, WS-Secure, WS-Reliable messaging and so on.

Is exposing CRUD operations through SOAP web services a bad idea? My instinct tells me that it is not least of which because the overhead of doing database calls overhead could be huge. I'm struggling to find documentation for/against this (anti)pattern so I was wondering if anyone could point me to some documentation or has an opinion on the matter. 

Also, if anyone knows of best practises (and/or documentation to that effect) when designing soap services, that would be great.

Here's an example of how the web service would look:

<ul>
<li>Create</li>
<li>Delete</li>
<li>Execute</li>
<li>Fetch</li>
<li>Update </li>
</ul>

And here's what the implementation would look like:

<pre><code>[WebMethod]
public byte[] Fetch(byte[] requestData)
{
 SelectRequest request = (SelectRequest)Deserialize(requestData);

 DbManager crudManager = new DbManager();
 object result = crudManager.Select(request.ObjectType, request.Criteria);

 return Serialize(result);
}
</code></pre>

Using SOAP to expose CRUD operations

通过SOAP web服务公开CRUD操作是个坏主意吗？我的直觉告诉我，这并不是最重要的，因为进行数据库调用的开销可能是巨大的。我正在努力寻找支持/反对这种(反)模式的文档，所以我想知道是否有人可以给我一些文档或者对这个问题有意见。此外，如果有人知道在设计soap服务时的最佳实践(和/或文档)，那就太好了。下面的示例展示...

问使用SOAP公开CRUD操作
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用SOAP公开CRUD操作EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用SOAP公开CRUD操作
EN