Revision history for SyndicatingWikka
Revision [23066]
Last edited on 2016-05-20 07:38:45 by DarTar [Replaces old-style internal links with new pipe-split links.]Additions:
~-trough some of its built-in [[RSSInfo | rss feeds]];
An action to automatically check for available upgrades only requires two simple pieces of code. On the server side, we just need a simple handler to output the version number of the latest stable package as raw text. From the client side, we need an action that connects to the Wikka server, retrieves the latest version number and compare it with the one of the engine running locally. If the local package is outdated, then an upgrade information box is displayed, along with automatically generated links. One can certainly provide more server-side information to be used by client wikis, e.g. a direct download link to the package in different formats, a link to the [[RecentChanges | changelog]] or the [[WhatsNew | "what's new"]] page. This would require a more flexible output format (XML) on the server side.
Now suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph | graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
An action to automatically check for available upgrades only requires two simple pieces of code. On the server side, we just need a simple handler to output the version number of the latest stable package as raw text. From the client side, we need an action that connects to the Wikka server, retrieves the latest version number and compare it with the one of the engine running locally. If the local package is outdated, then an upgrade information box is displayed, along with automatically generated links. One can certainly provide more server-side information to be used by client wikis, e.g. a direct download link to the package in different formats, a link to the [[RecentChanges | changelog]] or the [[WhatsNew | "what's new"]] page. This would require a more flexible output format (XML) on the server side.
Now suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph | graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
Deletions:
An action to automatically check for available upgrades only requires two simple pieces of code. On the server side, we just need a simple handler to output the version number of the latest stable package as raw text. From the client side, we need an action that connects to the Wikka server, retrieves the latest version number and compare it with the one of the engine running locally. If the local package is outdated, then an upgrade information box is displayed, along with automatically generated links. One can certainly provide more server-side information to be used by client wikis, e.g. a direct download link to the package in different formats, a link to the [[RecentChanges changelog]] or the [[WhatsNew "what's new"]] page. This would require a more flexible output format (XML) on the server side.
Now suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
No Differences
Additions:
CategoryDevelopmentDiscussion CategoryDevelopmentSyndication
Deletions:
Additions:
== A simple application: //automatically checking for updates// ==
An action to automatically check for available upgrades only requires two simple pieces of code. On the server side, we just need a simple handler to output the version number of the latest stable package as raw text. From the client side, we need an action that connects to the Wikka server, retrieves the latest version number and compare it with the one of the engine running locally. If the local package is outdated, then an upgrade information box is displayed, along with automatically generated links. One can certainly provide more server-side information to be used by client wikis, e.g. a direct download link to the package in different formats, a link to the [[RecentChanges changelog]] or the [[WhatsNew "what's new"]] page. This would require a more flexible output format (XML) on the server side.
Now suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
An action to automatically check for available upgrades only requires two simple pieces of code. On the server side, we just need a simple handler to output the version number of the latest stable package as raw text. From the client side, we need an action that connects to the Wikka server, retrieves the latest version number and compare it with the one of the engine running locally. If the local package is outdated, then an upgrade information box is displayed, along with automatically generated links. One can certainly provide more server-side information to be used by client wikis, e.g. a direct download link to the package in different formats, a link to the [[RecentChanges changelog]] or the [[WhatsNew "what's new"]] page. This would require a more flexible output format (XML) on the server side.
Now suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
Deletions:
Additions:
~-through the WikiPing functionality;
It would be interesting to explore the possibility of extending these tools to include other handlers, producing output in different formats (RDF, RSS, MM, raw text) to be used by external sites or services to syndicate the content of a wiki.
== An example of advanced syndication between wikis==
~&Logically it's only a kind of division between generating content and displaying it. I.e. having a function like FetchContent() who sorts out the (acess-)rights and calls the other funcs who will make the content. NilsLindenberg
It would be interesting to explore the possibility of extending these tools to include other handlers, producing output in different formats (RDF, RSS, MM, raw text) to be used by external sites or services to syndicate the content of a wiki.
== An example of advanced syndication between wikis==
~&Logically it's only a kind of division between generating content and displaying it. I.e. having a function like FetchContent() who sorts out the (acess-)rights and calls the other funcs who will make the content. NilsLindenberg
Deletions:
== An example of advanced syndication ==
~&Logically it's only a kind of division between generating content and displaying it. I.e. having a function like FetchContent() who sorts out the (acess-)rights and calls the other funcs who will make the content. And you've forgotten to mention wikiping NilsLindenberg
Additions:
~&Logically it's only a kind of division between generating content and displaying it. I.e. having a function like FetchContent() who sorts out the (acess-)rights and calls the other funcs who will make the content. And you've forgotten to mention wikiping NilsLindenberg
Additions:
>>I would like to collect on this page some thoughts about the development of advanced tools (a sort of ""<acronym title="Application Programming Interface">API</acronym>"") to allow **syndication** of content and/or structure of a wiki.
Deletions:
Additions:
>>I would like to collect on this page some thoughts about the development of advanced tools (a sort of ""<acronym title="Application Programming Interface">API</acronym>"") to allow **syndication** of the content and/or the structure of a wiki.
Deletions:
Additions:
== A Wikka API ==
== An example of advanced syndication ==
For example, suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
== Possible applications ==
== An example of advanced syndication ==
For example, suppose (B), (C), and (D) possess a handler outputting a RSS feed with the //number of new registered users per day during the last week//. (A) could use an action to syndicate (B), (C) and (D), process the data available from such feeds, and use something like a built-in [[BarGraph graphic class]] to output a chart comparing the evolution of the number of users for each of these wikis.
== Possible applications ==
Deletions:
Additions:
~1) process, format and display such information "locally".
Deletions:
Additions:
It would be interesting to explore the possibility of extending these tools to include other handlers, producing output in different formats (XML, RSS, MM, raw text) to be used by external sites or services to syndicate the content of a wiki.
Deletions:
Additions:
~-trough some of its built-in [[RSSInfo rss feeds]];
Deletions:
Additions:
>>I would like to collect on this page some thoughts about the development of advanced tools (a sort of API) to allow **syndication** of the content and/or the structure of a wiki.
Deletions:
Additions:
>>I would like to collect on this page some thoughts about the development of advanced tools (a sort of API) to **syndicate** the content and/or the structure of a wiki.
Deletions:
Additions:
~-wiki metadata (e.g., the number of pages on a wiki)
