Quoting from Sucking less, on a budget, for reasons that will be obvious to some: Beta A friend asked me today if Camino 1.1 was even in alpha. Heck, we’re on alpha two, but I guess we haven’t really done the best job of promoting it. To some extent, that’s reasonable, alphas generally aren’t the kind of thing you want your grandmother using. However, our standards are usually a little higher than
More than 5,000 organizations count on our digital courses and more to help their teams learn the tools and technologies that drive business outcomes. We can help yours too. New AI policy for O’Reilly authors and talent O’Reilly president Laura Baldwin shares the company’s ethical approach to leveraging GenAI tools and ensuring O’Reilly experts are compensated for their work. Read it now It’s time
このところ立て続けにドラフトが改訂されていたIETF版のAtom Syndication Formatが4月18日付のdraft-ietf-atompub-format-08をもってLast Callとされ、2~3週間のうちに最終判断を下すという段階に至った。 以前の草案で驚かされたhead要素は、3月半ばの改訂案で削除され、大きな枠組みは既存のAtom 0.3に近い形に戻った模様。昨年末に登場した草案と比べると、要素型名を含めて細部はかなり変更されているが、head要素以外は根本的な違いはなさそうだ。 今のところ世の中で提供されているAtomフィードのほとんどは0.3と呼ばれるフォーマットだと思われるが、うまくこのIETF版に移行していけるだろうか?
April 14, 2004 Joe Gregorio In my last article I covered the changes from version 7 to version 8 of the draft AtomAPI. Now the latest version of the AtomAPI is version 9 which adds support for SOAP. This change, and its impact on API implementers, will be covered in a future article. In this article I'm going to build a simple implementation of the AtomAPI. The first task at hand is to pick a viab
The Atom Publishing Protocol draft-ietf-atompub-protocol-03.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its
Contents RFC 5023 [.html] [.xml] To provide feedback on this draft join the atom-protocol mailing list. Other Information Rather than trying to keep up to date on all the activity in the Atom WG, I'll just send you over to look at the nice Atompub Status Pages that the IETF is now generating. Historical Info The previous version of the draft RFCs are available: draft-ietf-atompub-protocol-17 [.htm
December 17, 2003 Mark Pilgrim I wish I didn't need to write this article. My life would be much simpler if Atom could just use existing HTTP authentication, as-is. But it can't; I'm going to tell you why and then I'm going to tell you what we're doing instead. Let's back up. Atom, in case you missed it, is a new standard that uses XML over HTTP to publish and syndicate web-based content. It is in
See related links to what you are looking for.
After I'd finished with my PHP Atom API implementation, it made sense to try developing a client. Looking at the current discussion of PUT and DELETE versus just using GET and POST there was a general feeling that Javascript and DHTML couldn't support PUT and DELETE. Short history of XmlHttpRequest I'd previously read about something called XmlHttpRequest which allowed Javascript to connect to a s
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く