欧洲亚洲一区二区三区,在线亚洲+欧美+日本专区,国产亚洲精品自在久久

AJAX�|�站

spiders — Fri, 14 Apr 2006 01:31:00 GMT

�Q��?a >http://www.netvibes.com/

�W�三方个人首��：(x��)Netvibes

前一阵介�l�过一个自定义个�h首页服务ProtoPage�?a >Netvibes所提供的也是类似的服务�Q�比�q�它在功能上比ProtoPage要“Geek Style”的多，也更加适合Blogger使用�?br />
Netvibes的功能和界面可以说都是�݅取了Start.com�?a >iGoogle的精华�?br />
Netvibes的搜索模块可以搜索Google、Yahoo、MSN以及(qi��ng)WikiPedia。它的Feed��d��功能强大�Q�和Start.com非常�怼��Q�是一个完整的在线Feed Reader。Netvibes�q�可以像iGoogle那样��d��Gmail邮�g�Q�显�C�标题和邮�g摘要。它所提供的天气预报服务也优于Start.com和iGoogle�Q�可以显�C�全球主要城市的天气。另外，Netvibes�q�有一个WebNote便签功能�Q�方侉K��时记录，�?a >GDS里的Sidebar�c�M��?br />
和Start.com�c�M��的，Netvibes也支持直接��用或者登录用户��用，��d��后页面的改动都会(x��)保存在服务器�?br />
在界面上�Q�Netvibes也��用了AJAX�Q�可以在Internet Explorer和Firefox下拖曛_��个模块，�q�能够即时修攚w��面标题�?br />
MSN、Google又或者是Yahoo所提供的个人首��固然稳定，但是Netvibes�q�样的第三方服务却可以提供更高的灉|��性。对于同时��用多家网站服务的用户来说�Q�可能是更好的解��x��案�?br />

Netvibes :目前最��L(f��ng)��色的个性化首页之一;目前国内有okrss�Q�周博�?br />照搬了它的代码， Netvibes的代码写的的��很��l�，值得学习(f��n)�?br />
www.okrss.com
http://www.potu.com/my/

2.http://www.eskobo.com/default.aspx

spiders 2006-04-14 09:31 发表评论

spiders — Thu, 13 Apr 2006 08:30:00 GMT

From: http://www.scss.com.au/family/andrew/webdesign/xmlhttprequest/
/*

Cross-Browser XMLHttpRequest v1.2
=================================

Emulate Gecko 'XMLHttpRequest()' functionality in IE and Opera. Opera requires
the Sun Java Runtime Environment <http://www.java.com/>.

by Andrew Gregory
http://www.scss.com.au/family/andrew/webdesign/xmlhttprequest/

This work is licensed under the Creative Commons Attribution License. To view a
copy of this license, visit http://creativecommons.org/licenses/by-sa/2.5/ or
send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California
94305, USA.

Attribution: Leave my name and web address in this script intact.

Not Supported in Opera
----------------------
* user/password authentication
* responseXML data member

Not Fully Supported in Opera
----------------------------
* async requests
* abort()
* getAllResponseHeaders(), getAllResponseHeader(header)

*/
// IE support
if (window.ActiveXObject && !window.XMLHttpRequest) {
window.XMLHttpRequest = function() {
 var msxmls = new Array(
 'Msxml2.XMLHTTP.5.0',
 'Msxml2.XMLHTTP.4.0',
 'Msxml2.XMLHTTP.3.0',
 'Msxml2.XMLHTTP',
 'Microsoft.XMLHTTP');
 for (var i = 0; i < msxmls.length; i++) {
 try {
 return new ActiveXObject(msxmls[i]);
 } catch (e) {
 }
 }
 return null;
};
}
// Gecko support
/* ;-) */
// Opera support
if (window.opera && !window.XMLHttpRequest) {
window.XMLHttpRequest = function() {
 this.readyState = 0; // 0=uninitialized,1=loading,2=loaded,3=interactive,4=complete
 this.status = 0; // HTTP status codes
 this.statusText = '';
 this._headers = [];
 this._aborted = false;
 this._async = true;
 this._defaultCharset = 'ISO-8859-1';
 this._getCharset = function() {
 var charset = _defaultCharset;
 var contentType = this.getResponseHeader('Content-type').toUpperCase();
 val = contentType.indexOf('CHARSET=');
 if (val != -1) {
 charset = contentType.substring(val);
 }
 val = charset.indexOf(';');
 if (val != -1) {
 charset = charset.substring(0, val);
 }
 val = charset.indexOf(',');
 if (val != -1) {
 charset = charset.substring(0, val);
 }
 return charset;
 };
 this.abort = function() {
 this._aborted = true;
 };
 this.getAllResponseHeaders = function() {
 return this.getAllResponseHeader('*');
 };
 this.getAllResponseHeader = function(header) {
 var ret = '';
 for (var i = 0; i < this._headers.length; i++) {
 if (header == '*' || this._headers[i].h == header) {
 ret += this._headers[i].h + ': ' + this._headers[i].v + '\n';
 }
 }
 return ret;
 };
 this.getResponseHeader = function(header) {
 var ret = getAllResponseHeader(header);
 var i = ret.indexOf('\n');
 if (i != -1) {
 ret = ret.substring(0, i);
 }
 return ret;
 };
 this.setRequestHeader = function(header, value) {
 this._headers[this._headers.length] = {h:header, v:value};
 };
 this.open = function(method, url, async, user, password) {
 this.method = method;
 this.url = url;
 this._async = true;
 this._aborted = false;
 this._headers = [];
 if (arguments.length >= 3) {
 this._async = async;
 }
 if (arguments.length > 3) {
 opera.postError('XMLHttpRequest.open() - user/password not supported');
 }
 this.readyState = 1;
 if (this.onreadystatechange) {
 this.onreadystatechange();
 }
 };
 this.send = function(data) {
 if (!navigator.javaEnabled()) {
 alert("XMLHttpRequest.send() - Java must be installed and enabled.");
 return;
 }
 if (this._async) {
 setTimeout(this._sendasync, 0, this, data);
 // this is not really asynchronous and won't execute until the current
 // execution context ends
 } else {
 this._sendsync(data);
 }
 }
 this._sendasync = function(req, data) {
 if (!req._aborted) {
 req._sendsync(data);
 }
 };
 this._sendsync = function(data) {
 this.readyState = 2;
 if (this.onreadystatechange) {
 this.onreadystatechange();
 }
 // open connection
 var url = new java.net.URL(new java.net.URL(window.location.href), this.url);
 var conn = url.openConnection();
 for (var i = 0; i < this._headers.length; i++) {
 conn.setRequestProperty(this._headers[i].h, this._headers[i].v);
 }
 this._headers = [];
 if (this.method == 'POST') {
 // POST data
 conn.setDoOutput(true);
 var wr = new java.io.OutputStreamWriter(conn.getOutputStream(), this._getCharset());
 wr.write(data);
 wr.flush();
 wr.close();
 }
 // read response headers
 // NOTE: the getHeaderField() methods always return nulls for me :(
 var gotContentEncoding = false;
 var gotContentLength = false;
 var gotContentType = false;
 var gotDate = false;
 var gotExpiration = false;
 var gotLastModified = false;
 for (var i = 0; ; i++) {
 var hdrName = conn.getHeaderFieldKey(i);
 var hdrValue = conn.getHeaderField(i);
 if (hdrName == null && hdrValue == null) {
 break;
 }
 if (hdrName != null) {
 this._headers[this._headers.length] = {h:hdrName, v:hdrValue};
 switch (hdrName.toLowerCase()) {
 case 'content-encoding': gotContentEncoding = true; break;
 case 'content-length' : gotContentLength = true; break;
 case 'content-type' : gotContentType = true; break;
 case 'date' : gotDate = true; break;
 case 'expires' : gotExpiration = true; break;
 case 'last-modified' : gotLastModified = true; break;
 }
 }
 }
 // try to fill in any missing header information
 var val;
 val = conn.getContentEncoding();
 if (val != null && !gotContentEncoding) this._headers[this._headers.length] = {h:'Content-encoding', v:val};
 val = conn.getContentLength();
 if (val != -1 && !gotContentLength) this._headers[this._headers.length] = {h:'Content-length', v:val};
 val = conn.getContentType();
 if (val != null && !gotContentType) this._headers[this._headers.length] = {h:'Content-type', v:val};
 val = conn.getDate();
 if (val != 0 && !gotDate) this._headers[this._headers.length] = {h:'Date', v:(new Date(val)).toUTCString()};
 val = conn.getExpiration();
 if (val != 0 && !gotExpiration) this._headers[this._headers.length] = {h:'Expires', v:(new Date(val)).toUTCString()};
 val = conn.getLastModified();
 if (val != 0 && !gotLastModified) this._headers[this._headers.length] = {h:'Last-modified', v:(new Date(val)).toUTCString()};
 // read response data
 var reqdata = '';
 var stream = conn.getInputStream();
 if (stream) {
 var reader = new java.io.BufferedReader(new java.io.InputStreamReader(stream, this._getCharset()));
 var line;
 while ((line = reader.readLine()) != null) {
 if (this.readyState == 2) {
 this.readyState = 3;
 if (this.onreadystatechange) {
 this.onreadystatechange();
 }
 }
 reqdata += line + '\n';
 }
 reader.close();
 this.status = 200;
 this.statusText = 'OK';
 this.responseText = reqdata;
 this.readyState = 4;
 if (this.onreadystatechange) {
 this.onreadystatechange();
 }
 if (this.onload) {
 this.onload();
 }
 } else {
 // error
 this.status = 404;
 this.statusText = 'Not Found';
 this.responseText = '';
 this.readyState = 4;
 if (this.onreadystatechange) {
 this.onreadystatechange();
 }
 if (this.onerror) {
 this.onerror();
 }
 }
 };
};
}
// ActiveXObject emulation
if (!window.ActiveXObject && window.XMLHttpRequest) {
window.ActiveXObject = function(type) {
 switch (type.toLowerCase()) {
 case 'microsoft.xmlhttp':
 case 'msxml2.xmlhttp':
 case 'msxml2.xmlhttp.3.0':
 case 'msxml2.xmlhttp.4.0':
 case 'msxml2.xmlhttp.5.0':
 return new XMLHttpRequest();
 }
 return null;
};
}

spiders 2006-04-13 16:30 发表评论

RSS开发规�?英文|中文)

spiders — Thu, 13 Apr 2006 08:07:00 GMT

F E E D Validator

RSS 2.0 specification

Jump to navigation

From: http://feedvalidator.org/docs/rss2.html

What is RSS?
Sample files
About this document
Required channel elements
Optional channel elements
Elements of
Comments
Extending RSS
Roadmap
Copyright and disclaimer

What is RSS?

RSS is a Web content syndication format.

Its name is an acronym for Really Simple Syndication.

RSS is dialect of XML. All RSS files must conform to the XML 1.0 specification, as published on the World Wide Web Consortium (W3C) website.

At the top level, a RSS document is a element, with a mandatory attribute called version, that specifies the version of RSS that the document conforms to. If it conforms to this specification, the version attribute must be 2.0.

Subordinate to the element is a single element, which contains information about the channel (metadata) and its contents.

Sample files

Here are sample files for: RSS 0.91, 0.92 and 2.0.

Note that the sample files may point to documents and services that no longer exist. The 0.91 sample was created when the 0.91 docs were written. Maintaining a trail of samples seems like a good idea.

About this document

This document represents the status of RSS as of the Fall of 2002, version 2.0.1.

It incorporates all changes and additions, starting with the basic spec for RSS 0.91 (June 2000) and includes new features introduced in RSS 0.92 (December 2000) and RSS 0.94 (August 2002).

Change notes are here.

First we document the required and optional sub-elements of ; and then document the sub-elements of . The final sections answer frequently asked questions, and provide a roadmap for future evolution, and guidelines for extending RSS.

Required channel elements

Here's a list of the required channel elements, each with a brief description, an example, and where available, a pointer to a more complete description.

Element	Description	Example
title	The name of the channel. It's how people refer to your service. If you have an HTML website that contains the same information as your RSS file, the title of your channel should be the same as the title of your website.	GoUpstate.com News Headlines
link	The URL to the HTML website corresponding to the channel.	http://www.goupstate.com/
description	Phrase or sentence describing the channel.	The latest news from GoUpstate.com, a Spartanburg Herald-Journal Web site.

Optional channel elements

Here's a list of optional channel elements.

Element	Description	Example
language	The language the channel is written in. This allows aggregators to group all Italian language sites, for example, on a single page. A list of allowable values for this element, as provided by Netscape, is here. You may also use values defined by the W3C.	en-us
copyright	Copyright notice for content in the channel.	Copyright 2002, Spartanburg Herald-Journal
managingEditor	Email address for person responsible for editorial content.	geo@herald.com (George Matesky)
webMaster	Email address for person responsible for technical issues relating to channel.	betty@herald.com (Betty Guernsey)
pubDate	The publication date for the content in the channel. For example, the New York Times publishes on a daily basis, the publication date flips once every 24 hours. That's when the pubDate of the channel changes. All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).	Sat, 07 Sep 2002 0:00:01 GMT
lastBuildDate	The last time the content of the channel changed.	Sat, 07 Sep 2002 9:42:31 GMT
category	Specify one or more categories that the channel belongs to. Follows the same rules as the -level category element. More info.	Newspapers
generator	A string indicating the program used to generate the channel.	MightyInHouse Content System v2.3
docs	A URL that points to the documentation for the format used in the RSS file. It's probably a pointer to this page. It's for people who might stumble across an RSS file on a Web server 25 years from now and wonder what it is.	http://backend.userland.com/rss
cloud	Allows processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds. More info here.
ttl	ttl stands for time to live. It's a number of minutes that indicates how long a channel can be cached before refreshing from the source. More info here.	60
image	Specifies a GIF, JPEG or PNG image that can be displayed with the channel. More info here.
textInput	Specifies a text input box that can be displayed with the channel. More info here.
skipHours	A hint for aggregators telling them which hours they can skip. More info here.
skipDays	A hint for aggregators telling them which days they can skip. More info here.

sub-element of

is an optional sub-element of , which contains three required and three optional sub-elements.

is the URL of a GIF, JPEG or PNG image that represents the channel.

describes the image, it's used in the ALT attribute of the HTML tag when the channel is rendered in HTML. <link> is the URL of the site, when the channel is rendered, the image is a link to the site. (Note, in practice the image <title> and <link> should have the same value as the channel's <title> and <link>. Optional elements include <width> and <height>, numbers, indicating the width and height of the image in pixels. <description> contains text that is included in the TITLE attribute of the link formed around the image in the HTML rendering. Maximum value for width is 144, default value is 88. Maximum value for height is 400, default value is 31. <h3><cloud> sub-element of <channel><a id="ltcloudgtSubelementOfLtchannelgt" name="ltcloudgtSubelementOfLtchannelgt"></a></h3><cloud> is an optional sub-element of <channel>. It specifies a web service that supports the rssCloud interface which can be implemented in HTTP-POST, XML-RPC or SOAP 1.1. Its purpose is to allow processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds. <code><cloud domain="radio.xmlstoragesystem.com" port="80" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc" /></code> In this example, to request notification on the channel it appears in, you would send an XML-RPC message to radio.xmlstoragesystem.com on port 80, with a path of /RPC2. The procedure to call is xmlStorageSystem.rssPleaseNotify. A full explanation of this element and the rssCloud interface is <a >here</a>. <h3><ttl> sub-element of <channel><a id="ltttlgtSubelementOfLtchannelgt" name="ltttlgtSubelementOfLtchannelgt"></a></h3><ttl> is an optional sub-element of <channel>. ttl stands for time to live. It's a number of minutes that indicates how long a channel can be cached before refreshing from the source. This makes it possible for RSS sources to be managed by a file-sharing network such as <a >Gnutella</a>. Example: <ttl>60</ttl> <h3><textInput> sub-element of <channel><a id="lttextinputgtSubelementOfLtchannelgt" name="lttextinputgtSubelementOfLtchannelgt"></a></h3>A channel may optionally contain a <textInput> sub-element, which contains four required sub-elements. <title> -- The label of the Submit button in the text input area. <description> -- Explains the text input area. <name> -- The name of the text object in the text input area. <link> -- The URL of the CGI script that processes text input requests. The purpose of the <textInput> element is something of a mystery. You can use it to specify a search engine box. Or to allow a reader to provide feedback. Most aggregators ignore it. <hr /><h2>Elements of <item><a id="hrelementsOfLtitemgt" name="hrelementsOfLtitemgt"></a></h2>A channel may contain any number of <item>s. An item may represent a "story" -- much like a story in a newspaper or magazine; if so its description is a synopsis of the story, and the link points to the full story. An item may also be complete in itself, if so, the description contains the text (entity-encoded HTML is allowed), and the link and title may be omitted. All elements of an item are optional, however at least one of title or description must be present. <table cellspacing="10"><tbody><tr><th>Element</th><th>Description</th><th>Example</th></tr><tr><td valign="top">title</td><td valign="top">The title of the item.</td><td valign="top">Venice Film Festival Tries to Quit Sinking</td></tr><tr><td valign="top">link</td><td valign="top">The URL of the item.</td><td valign="top">http://www.nytimes.com/2002/09/07/movies/07FEST.html</td></tr><tr><td valign="top">description </td><td valign="top">The item synopsis.</td><td valign="top">Some of the most heated chatter at the Venice Film Festival this week was about the way that the arrival of the stars at the Palazzo del Cinema was being staged.</td></tr><tr><td valign="top">author</td><td valign="top">Email address of the author of the item. <a >More</a>.</td><td valign="top">oprah@oxygen.net</td></tr><tr><td valign="top">category</td><td valign="top">Includes the item in one or more categories. <a >More</a>.</td><td valign="top">Simpsons Characters</td></tr><tr><td valign="top">comments</td><td valign="top">URL of a page for comments relating to the item. <a >More</a>.</td><td valign="top">http://www.myblog.org/cgi-local/mt/mt-comments.cgi?entry_id=290</td></tr><tr><td valign="top">enclosure</td><td valign="top">Describes a media object that is attached to the item. <a >More</a>.</td><td valign="top"><enclosure url="http://live.curry.com/mp3/celebritySCms.mp3" length="1069871" type="audio/mpeg"/></td></tr><tr><td valign="top">guid</td><td valign="top">A string that uniquely identifies the item. <a >More</a>.</td><td valign="top"><guid isPermaLink="true">http://inessential.com/2002/09/01.php#a2</guid></td></tr><tr><td valign="top">pubDate</td><td valign="top">Indicates when the item was published. <a >More</a>.</td><td valign="top">Sun, 19 May 2002 15:21:36 GMT</td></tr><tr><td valign="top">source</td><td valign="top">The RSS channel that the item came from. <a >More</a>.</td><td valign="top">Quotes of the Day</source></td></tr></tbody></table> <h3> sub-element of <item><a id="ltsourcegtSubelementOfLtitemgt" name="ltsourcegtSubelementOfLtitemgt"></a></h3> is an optional sub-element of <item>. Its value is the name of the RSS channel that the item came from, derived from its <title>. It has one required attribute, url, which links to the XMLization of the source. <code>Tomalak's Realm</source></code> The purpose of this element is to propogate credit for links, to publicize the sources of news items. It's used in the post command in the Radio UserLand aggregator. It should be generated automatically when forwarding an item from an aggregator to a weblog authoring tool. <h3><enclosure> sub-element of <item><a id="ltenclosuregtSubelementOfLtitemgt" name="ltenclosuregtSubelementOfLtitemgt"></a></h3><enclosure> is an optional sub-element of <item>. It has three required attributes. url says where the enclosure is located, length says how big it is in bytes, and type says what its type is, a standard MIME type. The url must be an http url. <code><enclosure url="http://www.scripting.com/mp3s/weatherReportSuite.mp3" length="12216320" type="audio/mpeg" /></code> A use-case narrative for this element is <a >here</a> <h3><category> sub-element of <item><a id="ltcategorygtSubelementOfLtitemgt" name="ltcategorygtSubelementOfLtitemgt"></a></h3><category> is an optional sub-element of <item>. It has one optional attribute, domain, a string that identifies a categorization taxonomy. The value of the element is a forward-slash-separated string that identifies a hierarchic location in the indicated taxonomy. Processors may establish conventions for the interpretation of categories. Two examples are provided below: <code><category>Grateful Dead</category></code> <code><category domain="http://www.fool.com/cusips">MSFT</category></code> You may include as many category elements as you need to, for different domains, and to have an item cross-referenced in different parts of the same domain. <h3><pubDate> sub-element of <item><a id="ltpubdategtSubelementOfLtitemgt" name="ltpubdategtSubelementOfLtitemgt"></a></h3><pubDate> is an optional sub-element of <item>. Its value is a <a >date</a>, indicating when the item was published. If it's a date in the future, aggregators may choose to not display the item until that date. <code><pubDate>Sun, 19 May 2002 15:21:36 GMT</pubDate></code> <h3><guid> sub-element of <item><a id="ltguidgtSubelementOfLtitemgt" name="ltguidgtSubelementOfLtitemgt"></a></h3><guid> is an optional sub-element of <item>. guid stands for globally unique identifier. It's a string that uniquely identifies the item. When present, an aggregator may choose to use this string to determine if an item is new. <code><guid>http://some.server.com/weblogItem3207</guid></code> There are no rules for the syntax of a guid. Aggregators must view them as a string. It's up to the source of the feed to establish the uniqueness of the string. If the guid element has an attribute named "isPermaLink" with a value of true, the reader may assume that it is a <a >permalink</a> to the item, that is, a url that can be opened in a Web browser, that points to the full item described by the <item> element. An example: <code><guid isPermaLink="true">http://inessential.com/2002/09/01.php#a2</guid></code> isPermaLink is optional, its default value is true. If its value is false, the guid may not be assumed to be a url, or a url to anything in particular. <h3><comments> sub-element of <item><a id="ltcommentsgtSubelementOfLtitemgt" name="ltcommentsgtSubelementOfLtitemgt"></a></h3><comments> is an optional sub-element of <item>. If present, it is the url of the comments page for the item. <code><comments>http://rateyourmusic.com/yaccs/commentsn/blogId=705245&itemId=271</comments></code> <h3><author> sub-element of <item><a id="ltauthorgtSubelementOfLtitemgt" name="ltauthorgtSubelementOfLtitemgt"></a></h3><author> is an optional sub-element of <item>. It's the email address of the author of the item. For newspapers and magazines syndicating via RSS, the author is the person who wrote the article that the <item> describes. For collaborative weblogs, the author of the item might be different from the managing editor or webmaster. For a weblog authored by a single individual it would make sense to omit the <author> element. <code><author>lawyer@boyer.net (Lawyer Boyer)</author></code> <h2>Comments<a id="comments" name="comments"></a></h2>RSS places restrictions on the first non-whitespace characters of the data in <link> and <url> elements. The data in these elements must begin with an <a >IANA-registered</a> URI scheme, such as http://, https://, news://, mailto: and ftp://. Prior to RSS 2.0, the specification only allowed http:// and ftp://, however, in practice other URI schemes were in use by content developers and supported by aggregators. Aggregators may have limits on the URI schemes they support. Content developers should not assume that all aggregators support all schemes. In RSS 0.91, various elements are restricted to 500 or 100 characters. There can be no more than 15 <items> in a 0.91 <channel>. There are no string-length or XML-level limits in RSS 0.92 and greater. Processors may impose their own limits, and generators may have preferences that say no more than a certain number of <item>s can appear in a channel, or that strings are limited in length. In RSS 2.0, <a id="syndic8" name="syndic8">a provision</a> is made for linking a channel to its identifier in a cataloging system, using the channel-level category feature, described above. For example, to link a channel to its Syndic8 identifier, include a category element as a sub-element of <channel>, with domain "Syndic8", and value the identifier for your channel in the Syndic8 database. The appropriate category element for Scripting News would be <category domain="Syndic8">1765</category>. A frequently asked question about <guid>s is how do they compare to <link>s. Aren't they the same thing? Yes, in some content systems, and no in others. In some systems, <link> is a permalink to a weblog item. However, in other systems, each <item> is a synopsis of a longer article, <link> points to the article, and <guid> is the permalink to the weblog entry. In all cases, it's recommended that you provide the guid, and if possible make it a permalink. This enables aggregators to not repeat items, even if there have been editing changes. If you have questions about the RSS 2.0 format, please post them on the <a >RSS2-Support</a> mail list, hosted by Sjoerd Visscher. This is not a debating list, but serves as a support resource for users, authors and developers who are creating and using content in RSS 2.0 format. <h2>Extending RSS<a id="extendingRss" name="extendingRss"></a></h2>RSS originated in 1999, and has strived to be a simple, easy to understand format, with relatively modest goals. After it became a popular format, developers wanted to extend it using modules defined in namespaces, as <a >specified</a> by the W3C. RSS 2.0 adds that capability, following a simple rule. A RSS feed may contain elements not described on this page, only if those elements are defined in a namespace. The elements defined in this document are not themselves members of a namespace, so that RSS 2.0 can remain compatible with previous versions in the following sense -- a version 0.91 or 0.92 file is also a valid 2.0 file. If the elements of RSS 2.0 were in a namespace, this constraint would break, a version 0.9x file would not be a valid 2.0 file. Here's an <a >example</a> of a file that makes use of elements in namespaces, authored by Mark Pilgrim. <h2>Roadmap<a id="roadmap" name="roadmap"></a></h2>RSS is by no means a perfect format, but it is very popular and widely supported. Having a settled spec is something RSS has needed for a long time. The purpose of this work is to help it become a unchanging thing, to foster growth in the market that is developing around it, and to clear the path for innovation in new syndication formats. Therefore, the RSS spec is, for all practical purposes, frozen at version 2.0.1. We anticipate possible 2.0.2 or 2.0.3 versions, etc. only for the purpose of clarifying the specification, not for adding new features to the format. Subsequent work should happen in modules, using namespaces, and in completely new syndication formats, with new names. <h2>Copyright and disclaimer<a id="copyrightAndDisclaimer" name="copyrightAndDisclaimer"></a></h2><a id="copyright" name="copyright">© Copyright 1997-2002 UserLand Software. All Rights Reserved.</a> This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and these paragraphs are included on all such copies and derivative works. This document may not be modified in any way, such as by removing the copyright notice or references to UserLand or other organizations. Further, while these copyright restrictions apply to the written RSS specification, no claim of ownership is made by UserLand to the format it describes. Any party may, for commercial or non-commercial purposes, implement this format without royalty or license fee to UserLand. The limited permissions granted herein are perpetual and will not be revoked by UserLand or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and USERLAND DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. </div>  <a id="startnavigation" name="startnavigation"> </a> <div id="wmqeeuq" class="navbarContent" align="center"> </div> <a >Home</a> · <a >About</a> · <a >News</a> · <a >Docs</a> · <a >Terms</a> <div id="wmqeeuq" class="roundedCornerSpacer" align="center"> </div>  <div id="wmqeeuq" class="bottomCorners" align="left"> RSS 2.0 标准 来源�Q?a >http://www.cpcwedu.com/Document/WEBOfficial/095447158.htm</a> 什么是 RSS?<a target="_blank"></a>RSS 是一�U�站点内容聚合的格式�?br /> 它的名字�?em>Really Simple Syndication 的的��写�?/p>RSS是XML的一�U�。所有的RSS文档都遵�?<a target="_blank">XML 1.0规范</a>, 该规范发布在<a target="_blank">W3C</a>�|�站上�?/p><a target="_blank">�q�里</a>是RSS版本历史的一个概要�?br /> 在一个RSS文档中，最外层是一�?lt;rss>元素�Q�这个元素必��规定version属性，该属性明��了本文档遵从何�U�RSS版本规范。如果一个RSS文档以这个规范来表示�Q�那么它的version属性就必须�?.0�?/p><rss>元素只有一个子元素<channel>�Q�包含了关于�q�个频道(元数�?和它的内容的一些信息�?br /> ��h��文�g<a target="_blank"></a> �q�里有一些RSS��h��文�g�Q?RSS <a target="_blank">0.91</a>, <a target="_blank">0.92</a> �?<a target="_blank">2.0</a>�?br /> 注意�q�些��h��文�g所指向的链接地址和服务器可能已经不再存在。在撰写0.91文档的时候，�q�个0.91的样本文件就已经创徏了。维护一个样本文件的历史也许是一个不错的��L��?br /> 关于本文�?a target="_blank"></a> 本文档完成于2002�q�秋天，版本�?2.0.1�?br /> 它包含从 <a target="_blank">RSS 0.91</a> 规范(2000�q?开始的所有的修改和添加，以及(qi��ng)包含�?a target="_blank">RSS 0.92</a> �Q?000�q?2月）(j��)和RSS 0.94�Q?002�q?月）(j��)中的新的�Ҏ(gu��)��?br /> 详细的文档历史纪录请参阅<a target="_blank">�q�里</a>�?br /> 本文档中首先介绍必须的和可选的频道元素�Q�接着介绍�?lt;item>的子元素。最后回�{�了一些经常碰到的问题�Q��ƈ提供了未来的发展路线和RSS扩展的指导方针�?/p> 必需的频道元�?a target="_blank"></a> 下面是一个必��d��含的频道(channel)元素的列表，每一个都有一个简单的描述、一个例子、应该出现的位置和更详细描述的链接地址�?/p>01.●　title 名称�Q�title 描述�Q�频道的名称。它表明别�h如何讉K��你的服务。如果你有一个与你的RSS文�g内容一致的HTML�|�站�Q�你的title元素值应该与你的�|�站的标题相同�? 例子�Q�GoUpstate.com 的新��d��字标题�?02.●　link 名称�Q�link 描述�Q�对应频道的�|�站的URL链接地址�? 例子�Q�http://www.goupstate.com/ �?03.●　description 名称�Q�description 描述�Q�关于频道的描述�? 例子�Q�The latest news from GoUpstate.com, a Spartanburg Herald-Journal Web site�?/p>可选的频道元素<a target="_blank"></a> 下面是一个可选的频道(channel)元素的列表�?01.●　language 名称�Q�language 描述�Q�频道��用的语言。比如，在一个网站上�Q�允许聚合所有的意大利语站点到相应的分组。对于这个元素，可��用的��|��参阅 Netscape提供�?a target="_blank">清单</a>。或者可以参阅W3C定义�?<a target="_blank">清单</a>�? 例子�Q�en-us�?02.●　copyright 名称�Q�copyright 描述�Q�频道内容的版权声明�? 例子�Q�Copyright 2002, Spartanburg Herald-Journal 03.●　managingEditor 名称�Q�managingEditor 描述�Q�频道内容责�ȝ��辑的�?sh��)子邮�g地址�? 例子�Q�geo@herald.com (George Matesky) 04.●　webMaster 名称�Q�webMaster 描述�Q�频道技术支持�h员的�?sh��)子邮�g地址�? 例子�Q�betty@herald.com (Betty Guernsey) 05.●　pubDate 名称�Q�pubDate 描述�Q�频道内容发布的日期。所有的日期和时间都必须遵��@ <a target="_blank">RFC 822</a>规范, 但年份可以用�Q�个或４个字母表�C?首选４个字�?�? 例子�Q�Sat, 07 Sep 2002 00:00:01 GMT 06.●　lastBuildDate 名称�Q�lastBuildDate 描述�Q�频道内容的最后修�Ҏ(gu��)��间�? 例子�Q�Sat, 07 Sep 2002 09:42:31 GMT 07.●　category 名称�Q�category 描述�Q�指定频道所属的一个或多个分类。遵循与item�U�category元素相同的规则。详�?a target="_blank">�q�里</a>�? 例子�Q?lt;category>Newspapers</category> 08.●　generator 名称�Q�generator 描述�Q�表明生成频道的�E�序名称的字�W�串�? 例子�Q�MightyInHouse Content System v2.3 09.●　docs 名称�Q�docs 描述�Q�指向该RSS文�g所用格式说明文档的URL链接地址�? 例子�Q�http://blogs.law.harvard.edu/tech/rss�?10.●　cloud 名称�Q�cloud 描述�Q�允�?d��ng)R��过注册一个cloud来处理获得频道的更新通知�Q��ƈ为rss�U�子实现一个轻量��的发布订阅协议，详见<a target="_blank">�q�里</a>�? 例子�Q?lt;cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="pingMe" protocol="soap"/> 11.●　ttl 名称�Q�ttl 描述�Q�ttl是Time to live的羃写，表示生存旉��。它表示频道从源更新之前可以�~�存的时间。详�?<a target="_blank">�q�里</a>�? 例子�Q?lt;ttl>60</ttl>�?12.●　image 名称�Q�image 描述�Q�指定一个可以在频道中显�C�的GIF、JPEG或�?PNG 囑փ�。详�?a target="_blank">�q�里</a>�? 例子�Q��?/p>13.●　rating 名称�Q�rating 描述�Q�频道的 <a target="_blank">PICS</a> 内容分��信息�? 例子�Q?�?/p>14.●　textInput 名称�Q�textInput 描述�Q�指定一个可以在频道中显�C�的文本输入框。详�?a target="_blank">�q�里</a>�?br />例子�Q��?15.●　skipHours 名称�Q�skipHours 描述�Q�提�C��合器�Q�可以蟩�q�那些小时的旉��D�c(di��n)��详�?a target="_blank">�q�里</a>�?br />例子�Q��?16.●　skipDays 名称�Q�skipDays 描述�Q�提�C��合器�Q�可以蟩�q�那些天的时间段。详�?a target="_blank">�q�里</a>�? 例子�Q��?<channel>的子元素<image> <a target="_blank"></a> <image> �?<channel>的一个可选子元素, 它本�w�包含了三个必须的和三个可选的子元素�?/p><url>是一个GIF、JPEG或PNG囑փ�文�g的URL链接地址�Q�该囑փ�代表整个频道�?/p><title>用于描述上面的图像，当频道在HTML中显�C�时�Q�用于HTML语言中的的alt属性�?/p><link>是要�q�接的站点的url�Q�当昄��频道�Ӟ��囑փ�的连接指向该站点�?在实际中�Q?lt;title>�?lt;link>应该与频道的<title>�?lt;link>有相同的�?�?/p>可选的元素包括<width>�?lt;height>�Q�它们是数字�c�d��Q�指定图像的宽度和高度，单位为像素�?br /><description>��是link的TITLE属性中文本�Q�它?y��u)��在调用�|�页时显�C�出来�? 囑փ�宽度的最大��gؓ(f��)144�Q�默认��gؓ(f��)88 �?/p>囑փ�高度的最大��gؓ(f��)400�Q�默认��gؓ(f��)31 �?br /> <channel>的子元素<cloud><a target="_blank"></a> <cloud> �?<channel>的一个可选子元素�?/p>它指定一个可以支持rssCloud接口的web服务�Q�rssCloud接口可以在HTTP-POST、XML-RPC或SOAP1.1中实现�?/p>它的目的是允�?d��ng)R��过注册一个cloud来处理获得频道的更新通知�Q�从而�ؓ(f��)RSS feeds实现一个轻量��的发布订阅协�?<cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="myCloud.rssPleaseNotify" protocol="xml-rpc" /> 在这个例子中�Q��ؓ(f��)了请求频道通知�Q�你需要发送一个XML-RPC消息到rpc.sys.com�?0端口�Q��\径�ؓ(f��)/RPC2。调用的�E�序��Zؓ(f��)myCloud.rssPleaseNotify�?�q�个元素的详�l�说明和 rssCloud 接口说明请参�?<a target="_blank">�q�里</a>�?br /> <channel>子元�?lt;ttl><a target="_blank"></a> <ttl><channel>的一个可选子元素�?/p>ttl是Time to live的羃写，表示生存旉��。它表示频道从源重新更新之前可以�~�存的时间。这使得rss源可以被一个支持文件共享的�|�络所��理�Q�例�?a target="_blank">Gnutella</a>�?br /> 例子: <ttl>60</ttl> <channel>的子元素<textInput><a target="_blank"></a>频道可以选择包含一�?lt;textInput>子元素，它本�w�包含了四个必须的子元素�?/p><title>--文本输入区域提交按钮的标�{��?/p><description>--文本输入区域的描�q��?/p><name>--文本输入区域中文本对象的名称�?/p><link>--处理文本输入��h��的CGI脚本的URL链接地址�?/p>使用<textInput>元素的目的看��h��有些��秘。你可以用它提供一个搜索引擎输入框�Q�或让读者提供反馈信息。许多聚合器忽略该元素�?<item>的元�?a target="_blank"></a> 一个频道可以包含许�?lt;item>元素。一个项目可以代表一�?故事" ——比如说一份报�U�或杂志上的故事�Q�如果是�q�样的话�Q�那么项目的描述则是故事的摘要，��目的链接则指向整个故事的链接位�|�。一个项目也可以本��n是完整的�Q�如果是�q�样的话�Q�项目的描述��包含了文本(整体以HTML格式�~�码是可以的�Q�参�?<a target="_blank">例子</a>)�Q�而链接和标题可以省略。项目的所有元素都是可选的�Q�但是至��要包含一个标�?title)或描�q?description)�?01.●　title 名称�Q�title 描述�Q�item的标题�? 例子�Q�Venice Film Festival Tries to Quit Sinking 02.●　link 名称�Q�link 描述�Q�item的URL链接地址�? 例子�Q?a target="_blank">http://nytimes.com/2004/12/07FEST.html</a>03.●　description 名称�Q�description 描述�Q�item的摘要�? 例子�Q�Some of the most heated chatter at the Venice Film Festival this week was about the way that the arrival of the stars at the Palazzo del Cinema was being staged. 04.●　author 名称�Q�author 描述�Q�item作者的�?sh��)子邮�g地址。详�?a target="_blank">�q�里</a>�?br />例子�Q��?05.●　category 名称�Q�category 描述�Q�包含item在一个或多个分类中。详�?a target="_blank">�q�里</a>�? 例子�Q��?06.●　comments 名称�Q�comments 描述�Q�与item相关的评论的URL链接地址。详�?<a target="_blank">�q�里</a>�? 例子�Q��?07.●　enclosure 名称�Q�enclosure 描述�Q�item附加的媒体对象。详�?a target="_blank">�q�里</a>�?br />例子�Q��?08.●　guid 名称�Q�guid 描述�Q�可以唯一��定item�w�䆾的字�W�串。详�?<a target="_blank">�q�里</a>�?br />例子�Q��?09.●　pubDate 名称�Q�pubDate 描述�Q�item发布的时间。详�?<a target="_blank">�q�里</a>�?br />例子�Q��?10.●　source 名称�Q�source 描述�Q�rss频道来源。详�?<a target="_blank">�q�里</a>�?br />例子�Q��?<item>的子元素<a target="_blank"></a> �?lt;item>的一个可选子元素�?br /> 它的值是item所属rss频道的名�U�ͼ�从title衍生而来。它有一个必��d��含的属性url, 该属性链接到XML序列化源�?/p>Tomalak's Realm</source> 该元素的作用是提高链接的声望�Q�从而进一步推�q�新闻项目的源头。它可以用在聚合器的Post命��o(h��)中。当从聚合器中通过一个webblog�~�辑工具提交一个item�Ӟ��应该能够被自动生成�?br /> <item>的子元素<enclosure><a target="_blank"></a> <enclosure>�?lt;item>的一个可选子元素�?/p>它有三个必须的属性。url属性表明enclosure的位�|�，length属性表明它的字节大��，而type属性则指出它的标准MIME�c�d��?/p>�q�里的url必须��Z��个http url�? <enclosure url="http://www.scripting.com/mp3s/weatherReportSuite.mp3" length="12216320" type="audio/mpeg" /> 它的 use-case 说明请参�?a target="_blank">�q�里</a>�?br /> <item>的子元素<category><a target="_blank"></a> <category>�?lt;item>的一个可选子元素�?/p>它有一个可选属性domain�Q�该属性是一个用来定义分�c�L��的字�W�串�?该节点的值是一个斜杠分割的字符�Ԍ��它用来表明在指定的分�c�L��中的层次位置。处理器可以为分�cȝ��识别建立协定。以下是两个例子�Q? <category>Grateful Dead</category> <category domain="http://www.fool.com/cusips">MSFT</category> 你可以根据需要�ؓ(f��)不同的域包含很多<category>元素�Q��ƈ且可以在相同域的不同部分拥有一个交叉引用的item�? <item>的子元素<pubDate><a target="_blank"></a> <pubDate> �?lt;item>的一个可选子元素�?/p>它的值是一�?<a target="_blank">日期</a>, 表明��目发布的时间。如果它是一个将来的日期�Q�则聚合器在日期到达之前可以选择不显�C��目。�?br /> <pubDate>Sun, 19 May 2002 15:21:36 GMT</pubDate> <item>的子元素<guid> <a target="_blank"></a> <guid>�?lt;item>的一个可选子元素�?/p>guid �?globally unique identifier的羃写。它是一个可以唯一识别�q�个<item>的字�W�串。在发布之后�Q�聚合器可以选择使用该字�W�串判断�q�个<item>是否是新的。�?/p><guid>http://some.server.com/weblogItem3207</guid> guid没有特定的语法规则。聚合器必须��它们当作一个字�W�串来处理。生成具有唯一性的字符串guid取决于种子的源头�?如果guid元素有isPermaLink属性，�q�且��gؓ(f��)真，解释器就�?x��)认为它是item的permalink。permalink是一个可在web��览器中打开的url链接�Q�它指向<item>节点所描述的完整item�?例如�Q?/p><guid isPermaLink="true">http://inessential.com/2002/09/01.php#a2</guid>isPermaLink是可选属性，默认��gؓ(f��)真。如果��gؓ(f��)假，guid��不�?x��)被认��?f��)是一个url或指向�Q何对象的url�? <item>的子元素<comments><a target="_blank"></a> <comments>�?lt;item>的一个可选子元素�?/p>如果出现�Q�它指向与item相关的评论的url�?br /> <comments>http://ekzemplo.com/entry/4403/comments</comments> 更多信息�Q�请参阅 <a target="_blank">�q�里</a>�?br /> <item>的子元素<author> <a target="_blank"></a> <author>�?lt;item>的一个可选子元素�?/p>它是item作者的�?sh��)子邮�g地址l。对于通过rss传播的报�U�和杂志�Q�作者可能是写该item所描述的文章的人。对于聚集型webblogs�Q�作者可能不是责�ȝ��辑或站长。对于个人维护的webblog�Q�忽�?lt;author>节点是有意义的�?/p><author>lawyer@boyer.net (Lawyer Boyer)</author> 注释<a target="_blank"></a> RSS限制<link> �?<url>元素的数据首字母为非�I�格字符。这些元素的数据必须�?a target="_blank">IANA-registered</a> URI�Ҏ(gu��)��规定的格式开始，如http://, https://, news://, mailto:�?ftp://�{�。在RSS2.0规范之前�Q�RSS规范只允许http:// �?ftp://�Q�然而在实践中，其他的URI�Ҏ(gu��)��被内容开发者广泛��用，�q�被聚合器所支持。聚合器也许对它们支持的URI�Ҏ(gu��)��有一些限�Ӟ��而内容开发者不应该假定所有的聚合器都支持所有的URI�Ҏ(gu��)��?/p>�?RSS 0.91规范中，各种元素都被限制�?00�?00个字�W�。在一个符�?.91规范的频道中�Q�不能超�q?5�?<item> 元素。在RSS 0.92和以后的规范中，不再有这些字�W�长度或者XML�U�别的限制。处理器也许强加一些它们自��q��限制�Q��生者也许有自己的一些参数选择�Q�它们可以规定在一个频道中�Q�不��过一定数目的<item>元素�Q�或者字�W�串都限制在一定的长度。�?/p>如上所�q�ͼ�在 RSS 2.0规范中，对于一个目录系�l�，当链接一个频道到它的标识中时�Q��用基于频道��别的分类特征�?例如�Q�如果链接一个频道到它的Syndic8 标识�Q�则��包括一个分�c�d��素作为频道的子元素，它有域“Syndic8”属性，同时在Syndic8 数据库中��Z��的频道确定这个标识。正��的分类元素脚本应该�?<category domain="Syndic8">1765</category>�?br /> 一个经常被问到的问题是关于<guid> 如何�?<link>�q�行区别。它们指的是相同的事情吗�Q�在一些内容系�l�中是，但在别的内容�pȝ��中可能不是。在一些系�l�中�Q?lt;link>是一个网�l�日志项的永久链接。然后在别的�pȝ��中，每一�?lt;item>都是一个较长文章的摘要�Q?lt;link>指向�q�篇文章�Q��?lt;guid>则是�q�个�|�络日志入口的永久链接。在所有的情况下，��提供<guid>,如果可能的话�Q��ƈ使它成�ؓ(f��)一个永久链接。这使聚合着在内容发生变化时�Q�也不会(x��)出现重复��目成�ؓ(f��)可能�?/p>如果你对RSS 2.0规范的格式有��M��问题�Q�请向由Sjoerd Visscher�l�护的电(sh��)子邮件列�?a target="_blank">RSS2-Support</a>发送邮件。这个邮件列表不是一个技术辩论的列表�Q�而是一个针对作者和开发�h员在创徏和��用RSS 2.0格式的内�Ҏ(gu��)��提供技术支持的列表�?/p>RSS的扩�?a target="_blank"></a> RSS��h��?999�q�_(d��)��目标是成��Z��个简单、易于理解的数据格式。在它逐渐成�ؓ(f��)一�U�流行格式之后，开发者想在一个名字空间中使用模块对它�q�行扩展�Q�正像W3C<a target="_blank">定义</a>的那栗��?RSS遵��@��单的规则�Q�增加了它的能力。一个RSS feed 可以包含不是在本��中描述的内容，而只是在一个名字空间中定义的那些元素�?br />本文档中定义的元素不是一个名字空间本省的元素�Q�因此， RSS2.0从某�U�意义上来讲�Q�和原来的版本是兼容的，即一�?0.91 或�?0.92 版本的文件也是一个有效的 2.0 版本文�g。如果RSS2.0的元素是在一个名字空间中�Q�那么这�U�约束将被打��_(d��)��?一�?.9x 版本的文件不可能是一个有效的2.0 版本的文件�?br /> 发展方向<a name="roadmap"> </a> RSS决不是一个完��的格式�Q�但是它现在已经非常��行�Q��ƈ得到�q�泛的支持。要成�ؓ(f��)一个固定的规范�Q�RSS需要很长的一�D�|��间。这��工作的目的是帮助RSS成�ؓ(f��)一个固定的事情�Q�同时促�q�和培育围绕它进行的开发的市场的增长，�q��ؓ(f��)新的聚合格式铺��^道�\。因此，��Z��实用的目的，RSS规范?y��u)��被�ȝ��?.0.2版本。我们可以预期的可能�?.0.2 或�?2.0.3�{�版本，都只是出于澄清规范的目的�Q�而不是在格式上增加新的特征。后�l�的工作应该集中在模块化、名字空间的使用和在完全新的聚合格式中用新的名字�{�方面�?/p>许可协议和作�?a target="_blank"></a> RSS 2.0 是在遵��@i the Attribution/Share Alike Creative Commons <a target="_blank">许可协议</a> 的基��上由 the Berkman Center for Internet & Society at Harvard Law School 提供。本文档的作者是 Dave Winer�Q�UserLand software的创始�h�Q�也�?Berkman Center 的员工�?br /> </div>    <div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/spiders/" target="_blank">spiders</a> 2006-04-13 16:07 <a href="http://www.aygfsteel.com/spiders/archive/2006/04/13/40923.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div> </article> <article> spiders — Wed, 12 Apr 2006 00:54:00 GMT Meta 标签攑֜�每个�|�页�?lt;head>...</head>中，我们大家比较熟�?zh��n)�的如�Q��?br /> <meta name="GENERATOR" content="Microsoft FrontPage 3.0">说明�~�辑工具�Q?br /><meta name="KEYWORDS" content="...">说明关键词； <meta name="DESCRIPTION" content="...">说明主页描述�Q?br /> <meta http-equiv="Content-Type" content="text/html; charset=gb_2312-80">�?br /><meta http-equiv="Content-Language" content="zh-CN">说明所用语�a��?qi��ng)文�?.. 可见META有两�U�，name和http-equiv。�?br /> name主要用于描述�|�页,对应于content,以便于搜索引擎机器�h查找、分�c�（�?前几乎所有的搜烦(ch��)引擎都��用网上机器�h自动查找META值来�l�你的网��分�c�）(j��)。这其中最重要的是DESCRIPTION�Q�你的站点在引擎上的描述�Q�和KEYWORDS�Q�搜索引擎籍以分�cȝ��关键�?,应该�l�你的“每一��”都插入�q�两个META倹{��当然你也可以不要搜索引擎检�?可用: <meta name="ROBOTS" content="all | none | index | noindex | follow | nofollow"> 来确�? 讑֮��?all"时文件将被检索，且页上链接可被查�? 讑֮��?none"则表�C�文件不被检索，而且不查询页上的链接; 讑֮��?index"时文件将被检�? 讑֮��?follow"则可查询��上的链�? 讑֮��?noindex"时文件不��(g��)索，但可被查询链�? 讑֮��?nofollow"则表�C�文件不被检索，但可查询��上的链�? http-equiv��֐�思义相当于http文�g头的作用�Q�可以直接媄(ji��ng)响网��늚�传输。比�?直接的例子如: 1、自动刷斎ͼ��q�指向新�|�页 <meta http-equiv="Refresh" content="10; url= http://yourlink"> 10�U�后��h��到http://yourlink; 2、网��间转换时加入效�?br /><meta http-equiv="Page-Enter" content="revealTrans(duration=10, transition=50)"> <meta http-equiv="Page-Exit" content="revealTrans(duration=20, transition=6)"> 加在一个网��中�Q�进出时有一些特�D�效果，�q�个功能即FrontPage 98的Format/Page Transition.不过注意所加网��不能是一个Frame��? 3、强制网��不被存入Cache�?br /><meta http-equiv="pragma" content="no-cache"> <meta http-equiv="expires" content="wed, 26 Feb 1997 08:21:57 GMT"> 大家可以到http://www.internet.com上看看，它的首页当你断线后，��无法在cache中再调出。（本��n是关于徏站很��的站点) 4、定义指向窗�?br /><meta http-equiv="window-target" content="_top"> 可以防止�|�页被别��Z��Z��个Frame调用.(不过,我试了一�?��g��不灵) Meta�q�有很多功能, 如大家关心的 "怎样在搜索引擎中�Q�被攑֜�搜烦(ch��)�l�果前面�?位置"( http://vancouver-webpages.com/VWbot/mk-metas.html). 你可以在以下站点�q�一步查询：(x��)http://webdeveloper.com/categories/html/ html_metatag_res.html http://vancouver-webpages.com/META/ http://www.nlc-bnc.ca/ifla/II/metadata.htm <div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/spiders/" target="_blank">spiders</a> 2006-04-12 08:54 <a href="http://www.aygfsteel.com/spiders/archive/2006/04/12/40553.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div> </article> </main></body></html>