サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
ドラクエ3
www.prescod.net
There exists a persistent meme that XML is just a new-fangled, verbose form of s-expressions. For example, "XML is little more than a notation for trees and for tree grammars, a verbose variant of Lisp S-expressions coupled with a poor man's BNF (Backus-Naur form)" and " a poor copy of sexprs." These people do not appreciate that s-expressions were simply not designed to solve the same pr
Some thoughts about SOAP versus REST on Security REST is the underlying architecture of the World Wide Web and its two core specifications, URIs and HTTP. It has been proposedthat instead of using new-from-scratch Web Services technologies we can get much more bang for our buck by understanding the full generality of what we've got. A community has arisen around this idea and we spend our ti
Paul's REST Resources NEW: Combining a name and address into a single identifier Why doesn't REST have an object encoding? Vancouver XML User's Group slides A New Direction for Web Services -- XML Journal The extreme 2002 paper on the SOAP/REST controversy and associated slides. New: Thoughts on Web Services Choreography. New: XBind is a language for loading XML data into natural progr
Other problem domains (e.g. peer-to-peer software) are sometimes listed but there is no evidence that the Web Services world is making a concerted effort to solve them. EAI and B2B seem related but they vary radically in their details. The first is entirely within a single administrative domain. If a new protocol does not work perfectly, it can be ripped out and replaced. In the cross-busin
People implementing systems using REST often do not know how to translate their familiar state-transition diagrams into resources. This article shows how. Introduction The word "state" has two meanings -- these can be somewhat confusing. The first meaning of "state" is the data associated with an object. The second is like a "step" in a multi-step conversation or computation. The latter t
When designing your first REST system there are a variety of mistakes people often make. I want to summarize them so that you can avoid them. If any are unclear, ask for more information on rest-discuss. Using HTTP is not enough. You can use HTTP in a Web service without SOAP or XML-RPC and still do the logical equivalent of SOAP or XML-RPC. If you're going to use HTTP wrong you would actually be
このページを最初にブックマークしてみませんか？
『http://www.prescod.net/』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
