You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by st...@outerthought.org on 2003/10/06 16:00:07 UTC
[WIKI-UPDATE] GT2003HackathoncocoonCms GT2003HackathonFlow GT2003Hackathon GT2003HackathonJsr170 Mon Oct 6 16:00:06 2003
Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003HackathoncocoonCms , version: 3 on Mon Oct 6 13:56:16 2003 by BertrandDelacretaz
+
+ See also [Sylvain's weblog|http://www.anyware-tech.com/blogs/sylvain/archives/000073.html].
+
Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003HackathonFlow , version: 2 on Mon Oct 6 13:12:17 2003 by 157.193.102.50
- According to Sylvain this is possible, each coplet can have its own continuation. The only problem currently is that continuations which are not used might expire. Making a distinction between "refresh" (used to refresh pages only) and "active" continuations might help.
+ According to Sylvain this is possible, each coplet can have its own continuation. The only problem currently is that continuations which are not used might expire. Making a distinction between "refresh" (used to refresh pages only) and "active" continuations might help. And in addition, if only one coplet "continues", the other coplets should not execute any script code and perhaps even not the pipeline.
? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003Hackathon , version: 99 on Mon Oct 6 13:39:02 2003 by BertrandDelacretaz
- ! The quest for Cocoon's own Content Management. (Stefano)
+ ! The quest for [Cocoon's own Content Management|GT2003HackathoncocoonCms]. (Stefano)
? + ++++++++++++++++++++++++++
Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003HackathonJsr170 , version: 3 on Mon Oct 6 13:17:08 2003 by JeremyQuinn
- Problem: over 800 CMS vendors, currently each with their own API. JSR 170 aims to standardize access to content repositories.
+ Problem: over 800 CMS vendors, currently each with their own
+ Solution: API. JSR 170 aims to standardize access to content repositories.