I have been asked to set up a new web site which can be easily translated into any language (php, .NET, Java, Etc.) Of course, I can roll my roll, different types of content (XML / X-www-form-urledd (general post) / JSN / etc) can be accepted, but an existing method Or mechanism will definitely be advised to cut on time, for the service users. Confidence is spent on.
Accepts website modifications / sets (this is not just data retrieval), but it will be less likely to be too high (we estimate 2.5% set, 97.5) here is the provision of word service That protocol should go to HTTP, it should not be able to fully implement client speed (javascript in end-user browser etc.), because it contains specific user standard Require clarification.
Both are set and the parameters of the set parameter (usually 1 to 4) are very light-like methods (which I like only for choice), XML-RPC & amp; Soap (may be slightly overkill, but clearly defined methods and returns have the benefit) are generally suspected.
The most widely used 'spoken' and most easily applicable protocol in your opinion / experience is seen in different languages (from the perspective of consumers) who can meet this requirement? SOAP is a nightmare, almost any consumer except Java and / or .NET, and as long as things Changes, a Java client is a pain to talk to a .NET server (or vice versa). If you go on the SOAP route, then you send more and more to your web service users to be grateful for equipment support, because no one wants to deal with soap with hand.
You can write for a consumer much more restful web service in any language, because all its needs have an HTTP library, though in most things like content-type conversations for most mainstream languages There are libraries to help, etc. This is a big win for the Library Server, BTW.
A actually can be searched from the Restine API definition: The application of hypertext is one of the defining characteristics of state engine (Hateos) Rest, to be fair, It is usually ignored in the real world, mainly because it is overkill, like the cloud server management API or atom, some are actually a good example of a quiet service.
No matter what attitude you take, you should write a clear document on your own basis, on the auto-generated docs, there are useful references when these are necessary, but they are good, hands-written Do not take documents.
Comments
Post a Comment