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.
Deletions:
~-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.


Revision [18720]

Edited on 2008-01-28 00:12:33 by DarTar [Modified links pointing to docs server]

No Differences

Revision [12429]

Edited on 2005-12-26 10:27:38 by DarTar [adding category link]
Additions:
CategoryDevelopmentDiscussion CategoryDevelopmentSyndication
Deletions:
CategoryDevelopmentDiscussion


Revision [12422]

Edited on 2005-12-25 20:17:35 by DarTar [adding simple application example]
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.
Deletions:
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.


Revision [11627]

Edited on 2005-10-27 13:37:59 by DarTar [minor]
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
Deletions:
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.
== 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


Revision [11590]

Edited on 2005-10-26 13:12:42 by NilsLindenberg [reply to doctar ;)]
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


Revision [11579]

Edited on 2005-10-25 10:13:32 by DarTar [minor]
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:
>>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.


Revision [11578]

Edited on 2005-10-25 10:00:35 by DarTar [adding acronym]
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:
>>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.


Revision [11574]

Edited on 2005-10-25 09:35:40 by DarTar [stub]
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 ==
Deletions:
For example, suppose (B), (C), and (D) possess a handler outputting a RSS feed with the number of new registered users per day. (A) could use an action to syndicate (B), (C) and (D), process the data available from their 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.


Revision [11573]

Edited on 2005-10-25 09:33:48 by DarTar [stub]
Additions:
~1) process, format and display such information "locally".
Deletions:
~1) display such information locally.


Revision [11572]

Edited on 2005-10-25 09:33:01 by DarTar [stub]
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:
It would be interesting to explore the possibility of extending these tools to include other handlers, producing output in different formats (XML, RSS, raw text) to be used by external sites or services to syndicate the content of a wiki.


Revision [11571]

Edited on 2005-10-25 09:26:30 by DarTar [stub]
Additions:
~-trough some of its built-in [[RSSInfo rss feeds]];
Deletions:
~-trough some of the [[RSSInfo rss feeds]];


Revision [11570]

Edited on 2005-10-25 09:26:01 by DarTar [stub]
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:
>>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.


Revision [11569]

Edited on 2005-10-25 09:25:35 by DarTar [stub]
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:
>>I would like to collect on this page some thoughts about the development of advanced tools to **syndicate** the content and/or the structure of a wiki.


Revision [11568]

Edited on 2005-10-25 09:24:36 by DarTar [stub]
Additions:
~-wiki metadata (e.g., the number of pages on a wiki)
Deletions:
~-wiki metadata (e.g., the number of pages on a siki)


Revision [11567]

The oldest known version of this page was created on 2005-10-25 09:24:14 by DarTar [stub]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki