|
From: Garvin H. <gar...@us...> - 2004-04-04 15:22:52
|
Update of /cvsroot/php-blog/serendipity In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16148 Modified Files: README Log Message: fixed some more linefeeds Index: README =================================================================== RCS file: /cvsroot/php-blog/serendipity/README,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- README 21 Mar 2004 16:35:31 -0000 1.5 +++ README 4 Apr 2004 15:10:24 -0000 1.6 @@ -334,46 +334,46 @@ Serendipity supports an HTTP-cache compatible way of only showing items in an RSS feed which where modified since the last request from a -client. - +client. + Typically, an RSS reader fetches your RSS feeds (15 items, per default). It then remembers the timestamp when those items where fetched. By the time your RSS reader updates the feed (typically after 1 hour) Serendipity will now only serve all new or modified items since the last time of refresh. If no entries where updated since then, serendipity will only serve the 304 Header (Not Modified) and saves a lot of -bandwidth for both client and server on periodical updates. - +bandwidth for both client and server on periodical updates. + Technically an RSS reader catches the "Last-Modified" Header of the RSS output as well as a special "ETag"-Header. Both are set to the last modification time of your article base. On the next fetch, those received headers are sent as "IF_MODIFIED_SINCE" (= Last-Modified) and "IF_NONE_MATCH" (= ETag) Headers and will affect your rss feed. This -saves a lot of bandwidth on both client and server side. - +saves a lot of bandwidth on both client and server side. + Users who have been watching your feed and where not able to catch up the latest articles may miss some of them, because you usually only get 15 items per feed. In case your reader provides the IF_MODIFIED_SINCE header the client can now catch all items (resp. a maximum of 50 -articles to prevent abuse). - +articles to prevent abuse). + If you want to permanently disable that feature (whatever the reasons are) you can either set a "$_REQUEST['nocache'] = true" inside your -rss.php file (first line) or append the '&nocache=true' request variable +rss.php file (first line) or append the '&nocache=true' request variable to your feed so that it looks like: -http://example.host/serendipity/rss.php?version=2.0&nocache=true. - +http://example.host/serendipity/rss.php?version=2.0&nocache=true. + Of course, the usual feed behaviour is not affected if none of the caching headers are provided. So if you use syndication methods to embed content from a blog inside an application, just tune your application to either send the 'nocache'-Variable to a Serendipity blog, or to not send -the caching headers. - +the caching headers. + The syndication plugin can be configured to append that variable to your -feed URLs from your blog. - +feed URLs from your blog. + ######################################################################## - + Serendipity Weblog - http://s9y.org Licensed under the BSD License |
