You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Michael Wechner <mi...@wyona.org> on 2002/08/16 08:47:04 UTC
Wyona based on Slide's CM API
Hi
After some discussions we decided
that it's best to base Wyona's Content Management API on
the Slide API.
The have the following architecture in mind:
+-----------------------------------------+
| CLIENT |
| (HTTP, WebDAV, Other) |
+-----------------------------------------+
/|\ /|\
| |
\|/ |
+---------+---+ |
| COCOON | | |
| +-----+ | |
| | WYONA | |
+---+---------+ |
/|\ /|\ |
| | |
| \|/ \|/
| +-----------------+--------------+----+
| | SLIDE |WebDAV Servlet| |
| | (CM API) +--------------+ |
| +-------------------------------------+
| /|\
| |
\|/ \|/
+-------------------------------------------+
| DATA STORES |
| |
| +----------+ +----+ +------+ +-----+ |
| |Filesystem| |JDBC| |XML:DB| |Other| |
| +----------+ +----+ +------+ +-----+ |
+-------------------------------------------+
More information can be found at
http://www.wyona.org/docs/xdocs/architecture.html
Our first goal is to refactor and base our "Content/ResourceCreator" on
Slide API.Some use cases can be found here:
http://www.wyona.org/docs/xdocs/create-resource.html
In case you want to join our efforts you are certainly very welcome.
Thanks
Michi
P.S.: Maybe you like to discuss some stuff at the next OSCOM conference
at Berkeley
http://www.oscom.org/conferences/berkeley2002/index.html
http://marc.theaimsgroup.com/?l=slide-dev&m=102390630721859&w=2
Sorry, that we didn't know you before our first conference
http://marc.theaimsgroup.com/?l=slide-dev&m=101425426112058&w=2
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Wyona based on Slide's CM API
Posted by Stephan Michels <st...@apache.org>.
On Fri, 16 Aug 2002, Michael Wechner wrote:
>
>
> Stephan Michels wrote:
>
> > On Fri, 16 Aug 2002, Michael Wechner wrote:
> >
> >
> <snip/>
> >
> > We want to build a system based on Cocoon/Slide for a e-Learning(I hate
> > this word) solution. We have authors from different universities, which
> > should edit their content via WebDAV and XMLSpy. We also offers to write
> > their content with LaTex. At moment we use only the classes, which are
> > part of the current Cocoon HEAD. So we dont't have a Work Flow Manager, or
> > other part, which have commercial CMS included.
> >
> > http://www.vs-c.de/
>
> Every university nowadays is doing it's own "E-Learning" project ;-)
Yes, on the last Cebit I was impressed how many CMS and E-Learning
solutions exists. They should rename this into "CMS and others".
> > Perhaps we can profit from each other ;-)
>
> Yeah, I am sure: University of Zurich is using Wyona and they also
> have an "e-learning" project. But maybe we should rather discuss that
> off the mailing list.
I know, there was also group from the ETH member from our project.
> >>>But this will only run one machine in this combination. If you want to
> >>>run this in a cluster, you will have problems with the caching of the
> >>>Slide Stores.
> >>>
> >>What kind of cluster do you have in mind?
> >>
> >
> > For example, more than one instances of Cocoon(or the WebDAV Servlet) on
> > different machines combined with a LoadBlancer.
>
> What about replication of the data between the stores on different
> servers? Or did you mean that by caching?
Some stores caches the content, to minimize the interaction with the
back-end. For example, we use in our development the XMLDescriptorStore,
which not noticed, if another store modified the content of the
descriptors. So you must write an Store Proxy to support concurrency
actions, which also handles the transactions.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Wyona based on Slide's CM API
Posted by Michael Wechner <mi...@wyona.org>.
Stephan Michels wrote:
> On Fri, 16 Aug 2002, Michael Wechner wrote:
>
>
<snip/>
>
> We want to build a system based on Cocoon/Slide for a e-Learning(I hate
> this word) solution. We have authors from different universities, which
> should edit their content via WebDAV and XMLSpy. We also offers to write
> their content with LaTex. At moment we use only the classes, which are
> part of the current Cocoon HEAD. So we dont't have a Work Flow Manager, or
> other part, which have commercial CMS included.
>
> http://www.vs-c.de/
Every university nowadays is doing it's own "E-Learning" project ;-)
>
> Perhaps we can profit from each other ;-)
Yeah, I am sure: University of Zurich is using Wyona and they also
have an "e-learning" project. But maybe we should rather discuss that
off the mailing list.
>
>
>>>But this will only run one machine in this combination. If you want to
>>>run this in a cluster, you will have problems with the caching of the
>>>Slide Stores.
>>>
>>What kind of cluster do you have in mind?
>>
>
> For example, more than one instances of Cocoon(or the WebDAV Servlet) on
> different machines combined with a LoadBlancer.
What about replication of the data between the stores on different
servers? Or did you mean that by caching?
Michael
>
>
>>>These problems are solveable, but you must think about it.
>>>
>>Good to know
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Wyona based on Slide's CM API
Posted by Stephan Michels <st...@apache.org>.
On Fri, 16 Aug 2002, Michael Wechner wrote:
>
>
> Stephan Michels wrote:
>
> >
> >
> > On Fri, 16 Aug 2002, Michael Wechner wrote:
> >
> >
> >>Hi
> >>
> >>After some discussions we decided
> >>that it's best to base Wyona's Content Management API on
> >>the Slide API.
> >>
> >>The have the following architecture in mind:
> >>
> >>
> >>
> >>+-----------------------------------------+
> >>| CLIENT |
> >>| (HTTP, WebDAV, Other) |
> >>+-----------------------------------------+
> >> /|\ /|\
> >> | |
> >> \|/ |
> >>+---------+---+ |
> >>| COCOON | | |
> >>| +-----+ | |
> >>| | WYONA | |
> >>+---+---------+ |
> >> /|\ /|\ |
> >> | | |
> >> | \|/ \|/
> >> | +-----------------+--------------+----+
> >> | | SLIDE |WebDAV Servlet| |
> >> | | (CM API) +--------------+ |
> >> | +-------------------------------------+
> >> | /|\
> >> | |
> >> \|/ \|/
> >>+-------------------------------------------+
> >>| DATA STORES |
> >>| |
> >>| +----------+ +----+ +------+ +-----+ |
> >>| |Filesystem| |JDBC| |XML:DB| |Other| |
> >>| +----------+ +----+ +------+ +-----+ |
> >>+-------------------------------------------+
> >>
> >
> > Looks like the same architecture as we used at our project, except of the
> > wyona part ;-)
>
>
> Do you have more information on your project available?
We want to build a system based on Cocoon/Slide for a e-Learning(I hate
this word) solution. We have authors from different universities, which
should edit their content via WebDAV and XMLSpy. We also offers to write
their content with LaTex. At moment we use only the classes, which are
part of the current Cocoon HEAD. So we dont't have a Work Flow Manager, or
other part, which have commercial CMS included.
http://www.vs-c.de/
Perhaps we can profit from each other ;-)
> > But this will only run one machine in this combination. If you want to
> > run this in a cluster, you will have problems with the caching of the
> > Slide Stores.
>
> What kind of cluster do you have in mind?
For example, more than one instances of Cocoon(or the WebDAV Servlet) on
different machines combined with a LoadBlancer.
> > These problems are solveable, but you must think about it.
>
> Good to know
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Wyona based on Slide's CM API
Posted by Michael Wechner <mi...@wyona.org>.
Stephan Michels wrote:
>
>
> On Fri, 16 Aug 2002, Michael Wechner wrote:
>
>
>>Hi
>>
>>After some discussions we decided
>>that it's best to base Wyona's Content Management API on
>>the Slide API.
>>
>>The have the following architecture in mind:
>>
>>
>>
>>+-----------------------------------------+
>>| CLIENT |
>>| (HTTP, WebDAV, Other) |
>>+-----------------------------------------+
>> /|\ /|\
>> | |
>> \|/ |
>>+---------+---+ |
>>| COCOON | | |
>>| +-----+ | |
>>| | WYONA | |
>>+---+---------+ |
>> /|\ /|\ |
>> | | |
>> | \|/ \|/
>> | +-----------------+--------------+----+
>> | | SLIDE |WebDAV Servlet| |
>> | | (CM API) +--------------+ |
>> | +-------------------------------------+
>> | /|\
>> | |
>> \|/ \|/
>>+-------------------------------------------+
>>| DATA STORES |
>>| |
>>| +----------+ +----+ +------+ +-----+ |
>>| |Filesystem| |JDBC| |XML:DB| |Other| |
>>| +----------+ +----+ +------+ +-----+ |
>>+-------------------------------------------+
>>
>
> Looks like the same architecture as we used at our project, except of the
> wyona part ;-)
Do you have more information on your project available?
>
> But this will only run one machine in this combination. If you want to
> run this in a cluster, you will have problems with the caching of the
> Slide Stores.
What kind of cluster do you have in mind?
> These problems are solveable, but you must think about it.
Good to know
Thanks
Michael
>
> My 2 cents, Stephan Michels.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Wyona based on Slide's CM API
Posted by Stephan Michels <st...@apache.org>.
On Fri, 16 Aug 2002, Michael Wechner wrote:
> Hi
>
> After some discussions we decided
> that it's best to base Wyona's Content Management API on
> the Slide API.
>
> The have the following architecture in mind:
>
>
>
> +-----------------------------------------+
> | CLIENT |
> | (HTTP, WebDAV, Other) |
> +-----------------------------------------+
> /|\ /|\
> | |
> \|/ |
> +---------+---+ |
> | COCOON | | |
> | +-----+ | |
> | | WYONA | |
> +---+---------+ |
> /|\ /|\ |
> | | |
> | \|/ \|/
> | +-----------------+--------------+----+
> | | SLIDE |WebDAV Servlet| |
> | | (CM API) +--------------+ |
> | +-------------------------------------+
> | /|\
> | |
> \|/ \|/
> +-------------------------------------------+
> | DATA STORES |
> | |
> | +----------+ +----+ +------+ +-----+ |
> | |Filesystem| |JDBC| |XML:DB| |Other| |
> | +----------+ +----+ +------+ +-----+ |
> +-------------------------------------------+
Looks like the same architecture as we used at our project, except of the
wyona part ;-)
But this will only run one machine in this combination. If you want to
run this in a cluster, you will have problems with the caching of the
Slide Stores. These problems are solveable, but you must think about it.
My 2 cents, Stephan Michels.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org