I have 2 websites (www.mysite1.com and myweb2.com) both sites are in SSP server with SSP server Backend) and I want to pass data from one site to another. Now I am confused to using a web service or a form (on myweb2 from a page on myweb2)
Can anyone tell me one of the websites and websites, which is SOAP protocol Uses XML, which they send messages back and forth.
Using the post, on the other hand, is mostly associated with, and as an example of such a protocol, look at the HTTP post, you can post complicated XML, but People use plain post to simplify calling, and use them as answers. You do not need any additional software, probably, all the webkits have not got HTTP support. My own side bends towards the first half, if you are surprised by using HATEOAS, you can create a really good infrastructure for self-aware systems which, in real time as opposed by SOP, modify themselves with load and availability. , And it is in the middle of the argument for this; HTTP was designed for mass distributed networks, dealing with performance and stability. Soap happens on one-stop if it breaks-you have a few things (again, remember my bias. I wrote a lot on my blog, especially more.)
There is a great debate which is "better", for which I can only say "it relies entirely on what you want to do, how you like it, what you should do for it, your environment , Your experience, the sun's position and a few Arma, and the mood of my cat. "Eh, which means, a lot.
I am for a healthy debate about this, but I think SOAP is a reconsideration; Soap is an envelope with a header and body, and if it sounds familiar, then how it was actually designed to HTML, actually few people see it. Just one protocol is well understood and very well supported to change the stuff in the form of HTTP, and SOAP uses it to move its XML envelope around it. Is there a real difference between changing SOAP and HTML? Well, yes, the big difference is that SOAP rearranges all problems of HTTP (caching, addressability, state, scaling), and then uses HTTP to send messages and not to do anything, and stack them with samples Have to deal with first. Therefore, a lot of the goodness of the HTTPS has been ignored and reproduced in the second layer (hence, you need a SOAP stack to deal with it), which connects useless, ignorant and complexity to me. Are there.
Next What do you want to do? For really complex things, there are lots of standards in the webservices stack (I think there are approximately 1200 pages by adding them these days) that can help you, but If your needs are more polite (i.e. that crazy about complex security, for example) a simple post of a request (or GET) and an envelope with the result could be quite good back Is in HTTP The result is, as you probably know, HTTP content-type, many are already supported but you can create your own, for example / xml + myformat (or more correctly, application / x- Xml + myformat if i remember right) Receive the request, if this response code is 200, and is parsed.
Both will work on a heavy (WS- * stack) based on your heavy needs, the second and lightest and already supported. The rest is glue, as they say, as they say.
Comments
Post a Comment