Michael Wechner wrote:
Andreas Hartmann wrote:
Michael Wechner wrote:
Andreas Hartmann wrote:
With the current Lenya 1.4, this would mean to implement a custom
DocumentIdToPathMapper and a custom SiteManager.
But - do we really want to allow editing a Forrest site?
sure. No offense, but if Lenya isn't able to do this, then Lenya is
pretty useless. If Lenya doesn't allow building a Forrest publication,
then I think we have totally missed the goal of providing a Content
Management Framework
I don't think that we will be able to support all existing content
storage mechanisms.
the framework should be flexible enough that one is able to implement
it's own content storage. It's the same with URL spaces ....
Completely right, it just has to implement the content repository
API and Lenya will be happy.
We should be careful not to lose ourselves in
flexibility. We can't foresee all scenarios anyway.
Flexibility doesn't mean we have to implement all scenarios, but
provide interfaces which allow various scenarios. I guess the minimal
interface would be
InputStream getInputStream
OutputStream getOutputStream
A framework is
not a Swiss army knife.
why not?
:-)
For special scenarios, special solutions can be found.
In the case of Forrest - how about implementing a custom generator
which provides a read-only view of the Lenya repository which resembles
the Forrest file system?
I think Lenya should be able to read and write to Forrest. Again no offense
and please apologize for sounding harsh, but I think if Lenya is not able
to provide such interfaces it's really useless.
I think the introduction of a standardized storage API will not impair
Lenya's flexibility or deter Lenya from interacting with Forrest or any
other application. But it simplifies the future development ...
- Felix
Michi
That would only require one change to the
Forrest application (re-configuring the file generator).
-- Andreas
--
Felix Röthenbacher [EMAIL PROTECTED]
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
