You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Oliver Zeigermann <oz...@c1-fse.de> on 2003/11/18 12:02:31 UTC
Features of Slide 2.0 release
Issues:
1.) What features not yet implemented should go into the Slide 2.0 release?
2.) What needs to be fixed in order to have a first milestone release?
3.) What is in already in the pipeline?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Oliver Zeigermann wrote:
>> 1.) What features not yet implemented should go into the Slide 2.0
>> release?
>
>
> Tx caching in ExtendedStore does not have locking, but relies on the
> cached store for correctness. If the store does not use a conservative
> locking protocol isolation might be compromised.
A solution to this might be the global locking discussed in the other
thread. This would also enable lower isolation levels in the store tier.
Another solution would be to add non-blocking locks directly to the
cache. This is complicated and error-prone, but would allow for a write
back caching protocol as a side effect.
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
> 1.) What features not yet implemented should go into the Slide 2.0 release?
Tx caching in ExtendedStore does not have locking, but relies on the
cached store for correctness. If the store does not use a conservative
locking protocol isolation might be compromised.
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Stefano Mazzocchi <st...@apache.org>.
On 18 Nov 2003, at 03:45, Daniel Florey wrote:
> Am Dienstag, 18. November 2003 12:02 schrieb Oliver Zeigermann:
>> Issues:
>>
>> 1.) What features not yet implemented should go into the Slide 2.0
>> release?
> - Extendable event mechanism (that is essenital for 'inverted caching'
> in the
> presentation layer or to distribute changes in a clustered environment)
+1
> - Implement fast searching capabilities (properties and full text
> search,
> perhaps using lucene)
+0, it would be nice but it could take a long time, it's not high
priority for me ATM therefore I would not commit resources to implement
it.
> - Add global internal locking to improve concurrent modifications. At
> the
> moment this is delegated to the underlying stores and can not be easyly
> configured consistently for the whole system if different stores are
> used.
+1,
>> 2.) What needs to be fixed in order to have a first milestone release?
> - Getting the stores to work as expected (at least file/db-stores)
+1
> - Improve and fix or disable caching. It's not fully transactional in
> some
> places and can be improved (e.g. permission-cache)
I would be in favor of disabling caching for 2.0, then work on it to
improve speed. Functionality first, speed later.
> - Documentation...
yeah :-)
--
Stefano.
Re: Features of Slide 2.0 release
Posted by Daniel Florey <df...@c1-fse.de>.
Am Dienstag, 18. November 2003 12:02 schrieb Oliver Zeigermann:
> Issues:
>
> 1.) What features not yet implemented should go into the Slide 2.0 release?
- Extendable event mechanism (that is essenital for 'inverted caching' in the
presentation layer or to distribute changes in a clustered environment)
- Implement fast searching capabilities (properties and full text search,
perhaps using lucene)
- Add global internal locking to improve concurrent modifications. At the
moment this is delegated to the underlying stores and can not be easyly
configured consistently for the whole system if different stores are used.
> 2.) What needs to be fixed in order to have a first milestone release?
- Getting the stores to work as expected (at least file/db-stores)
- Improve and fix or disable caching. It's not fully transactional in some
places and can be improved (e.g. permission-cache)
- Documentation...
> 3.) What is in already in the pipeline?
>
>
> Oliver
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Oliver Zeigermann wrote:
> 3.) What is in already in the pipeline?
Binding implementation for tx file store is in my pipeline. Could be
augmented to include j2ee store.
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Oliver Zeigermann wrote:
> 1.) What features not yet implemented should go into the Slide 2.0 release?
I observed a lot of overhead in MacroImpl when copying, moving and
deleting resources. I thought it might be a good idea have some sort of
tunneling of this upper tier task to the store itself. A sub-interface
to Store like TunnelingStore might implement these actions optimized to
its nature. E.g. an SQL-store, might do updates (there currently is not
a single update in the j2ee proposal) or a combined deletes. The Tamino
store certainly has potential for optimizations like these as well.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Daniel Florey <df...@c1-fse.de>.
Am Dienstag, 18. November 2003 15:41 schrieb Martin Holz:
> Oliver Zeigermann <oz...@c1-fse.de> writes:
> > Oliver Zeigermann wrote:
> > > 1.) What features not yet implemented should go into the Slide 2.0
> > > release?
> >
> > If Slide is considered a content repository as a combination of
> > underlying stores, global locks that live for the duration of a
> > transaction might be considered. A generic multilevel lock
> > implementation already exists for the tx store and can easily be
> > reused in a non-blocking mode. A problem may be lock propagation to
> > parent resources if needed. Intention locks might discussed...
>
> How do transactions and the WebDAV protocol work together?
> Do you want transactions across several requests?
There is no support for transactions in WebDAV at the moment. But slide itself
provides transactional support. This is a good thing if some actions are
bundled on server side.
It would be possible to extend the WebDAV protocol with transaction support. I
don't think it is necessary and perhaps it has the disadvantage that a client
can use it for long term transactions. As far as I understood this should be
achieved by deltaV (workspace). On the other hand it would be nice to have
such a feature to enable updating several relating documents at once.
Daniel
>
> Martin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Stefano Mazzocchi <st...@apache.org>.
On 18 Nov 2003, at 06:41, Martin Holz wrote:
> Oliver Zeigermann <oz...@c1-fse.de> writes:
>
>> Oliver Zeigermann wrote:
>>> 1.) What features not yet implemented should go into the Slide 2.0
>>> release?
>>
>> If Slide is considered a content repository as a combination of
>> underlying stores, global locks that live for the duration of a
>> transaction might be considered. A generic multilevel lock
>> implementation already exists for the tx store and can easily be
>> reused in a non-blocking mode. A problem may be lock propagation to
>> parent resources if needed. Intention locks might discussed...
>
> How do transactions and the WebDAV protocol work together?
> Do you want transactions across several requests?
yes, that's done thru the "workspace" concept in DeltaV.
- create workspace
- do bunch of requests
- commit workspace
in case of a problem, the entire set of changes has to be rolled back.
--
Stefano.
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
My try of a summary of the links:
- Sometimes more than one request shall be processed atomically
- There are two possibilities to do so
- Transaction begin, commit, rollback methods
- Batch processing
- Transactions spanning multiple requests might be a thread to
concurrent access
- Bacht processing does not allow for simulated transaction behavior as
needed by clients
- Some pepople think transactions do not fit the HTTP philisophy as it
makes some requests dependent on others
- From a client view working-resource and workspace both provide means
for long-term transactions (my addition: might be too expensive for
short-term transactions)
Guido Casper wrote:
> Martin Holz wrote:
>>How do transactions and the WebDAV protocol work together?
>>Do you want transactions across several requests?
>
> FWIW, you may want to have a look at these links:
> http://lists.w3.org/Archives/Public/w3c-dist-auth/2002JulSep/0172.html
> http://lists.w3.org/Archives/Public/w3c-dist-auth/2002JulSep/thread.html
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Guido Casper <gc...@s-und-n.de>.
Martin Holz wrote:
> Oliver Zeigermann <oz...@c1-fse.de> writes:
>
>> Oliver Zeigermann wrote:
>>> 1.) What features not yet implemented should go into the Slide 2.0
>>> release?
>>
>> If Slide is considered a content repository as a combination of
>> underlying stores, global locks that live for the duration of a
>> transaction might be considered. A generic multilevel lock
>> implementation already exists for the tx store and can easily be
>> reused in a non-blocking mode. A problem may be lock propagation to
>> parent resources if needed. Intention locks might discussed...
>
> How do transactions and the WebDAV protocol work together?
> Do you want transactions across several requests?
FWIW, you may want to have a look at these links:
http://lists.w3.org/Archives/Public/w3c-dist-auth/2002JulSep/0172.html
http://lists.w3.org/Archives/Public/w3c-dist-auth/2002JulSep/thread.html
Guido
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Mike Oliver <ol...@matrix-media.com>.
For me, YES!!! Transactions that span several requests are useful for
Compound Documents where more than one file is contained in one document
and you don't want to add a version to one of these files unless all are
versioned.
Ollie
Martin Holz wrote:
>Oliver Zeigermann <oz...@c1-fse.de> writes:
>
>
>
>>Oliver Zeigermann wrote:
>>
>>
>>>1.) What features not yet implemented should go into the Slide 2.0 release?
>>>
>>>
>>If Slide is considered a content repository as a combination of
>>underlying stores, global locks that live for the duration of a
>>transaction might be considered. A generic multilevel lock
>>implementation already exists for the tx store and can easily be
>>reused in a non-blocking mode. A problem may be lock propagation to
>>parent resources if needed. Intention locks might discussed...
>>
>>
>
>How do transactions and the WebDAV protocol work together?
>Do you want transactions across several requests?
>
>Martin
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: slide-dev-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Martin Holz wrote:
> Oliver Zeigermann <oz...@c1-fse.de> writes:
>
>
>>Oliver Zeigermann wrote:
>>
>>>1.) What features not yet implemented should go into the Slide 2.0 release?
>>
>>If Slide is considered a content repository as a combination of
>>underlying stores, global locks that live for the duration of a
>>transaction might be considered. A generic multilevel lock
>>implementation already exists for the tx store and can easily be
>>reused in a non-blocking mode. A problem may be lock propagation to
>>parent resources if needed. Intention locks might discussed...
>
>
> How do transactions and the WebDAV protocol work together?
> Do you want transactions across several requests?
Hmmm. I was talking about the transaction started when a request is
processed. If we have a global lock on the resource(s) concerned *for
the duration of this single request* we might save us a lot of trouble
in lower tiers, i.e. the stores. That's what I wanted to say.
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Martin Holz <ho...@fiz-chemie.de>.
Oliver Zeigermann <oz...@c1-fse.de> writes:
> Oliver Zeigermann wrote:
> > 1.) What features not yet implemented should go into the Slide 2.0 release?
>
> If Slide is considered a content repository as a combination of
> underlying stores, global locks that live for the duration of a
> transaction might be considered. A generic multilevel lock
> implementation already exists for the tx store and can easily be
> reused in a non-blocking mode. A problem may be lock propagation to
> parent resources if needed. Intention locks might discussed...
How do transactions and the WebDAV protocol work together?
Do you want transactions across several requests?
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Oliver Zeigermann wrote:
> 1.) What features not yet implemented should go into the Slide 2.0 release?
If Slide is considered a content repository as a combination of
underlying stores, global locks that live for the duration of a
transaction might be considered. A generic multilevel lock
implementation already exists for the tx store and can easily be reused
in a non-blocking mode. A problem may be lock propagation to parent
resources if needed. Intention locks might discussed...
As discussed earlier in this mailing list and as Daniel already noticed,
this is not needed for correctness, but might reduce the danger of
deadlocks to a more reasonable level and enables reporting of conflicts
on a pre-store tier.
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Stefano Mazzocchi <st...@apache.org>.
On 18 Nov 2003, at 03:10, Richard Unger wrote:
>> Oliver Zeigermann wrote:
>>> 1.) What features not yet implemented should go into the Slide 2.0
>> release?
>>
>> There has been a patch JTA patch proposed by Grant Gongaware some time
>> ago. This made the transaction manager implmentation configurable to
>> use
>> the containers instead of Slides integratied TM. It also included some
>> patches moving certain read actions inside transactions.
>>
>> While these patches cetainly are valuable (ah, need to check them and
>> add Grant to the contributors list) the concept of using external TMs
>> is
>> to be discussed. The idea of connectors to plug Slide into J2EE
>> containers come up more than once as well. However, this is a bit
>> tricky
>> as Slide needs a web container (not a full J2EE container) to run in
>> the
>> first place. This would mean you might have two containers running.
>> Isn't that weird?
>>
>> This really is a philosophical question, I guess. Is Slide something
>> like a document repository that can be connected to a J2EE container
>> just like an RDBMS? Or is it an integrated part of a J2EE container
>> resp. web container (like Tomcat)?
>>
>
> I think attacking the full container integration is too big a task if
> we want a
> 2.0 release early next year.
> And in any case a J2EE / Servlet Container is 'well specified'. There
> is no
> specification, as far as I am aware, for a WEBDAV based J2EE
> container. It
> sounds neat, but big and complicated. I think staying focused is
> important if
> we want to make a release...
big +1, let's keep the contract as the Servlet API which is solid, well
known and portable. Remember, 2.0 is not the end but just the beginning
of Slide's new life ;-) if new needs emerge, we follow them.
--
Stefano.
Re: Features of Slide 2.0 release
Posted by Richard Unger <ru...@cim.mcgill.ca>.
> Oliver Zeigermann wrote:
> > 1.) What features not yet implemented should go into the Slide 2.0
> release?
>
> There has been a patch JTA patch proposed by Grant Gongaware some time
> ago. This made the transaction manager implmentation configurable to use
> the containers instead of Slides integratied TM. It also included some
> patches moving certain read actions inside transactions.
>
> While these patches cetainly are valuable (ah, need to check them and
> add Grant to the contributors list) the concept of using external TMs is
> to be discussed. The idea of connectors to plug Slide into J2EE
> containers come up more than once as well. However, this is a bit tricky
> as Slide needs a web container (not a full J2EE container) to run in the
> first place. This would mean you might have two containers running.
> Isn't that weird?
>
> This really is a philosophical question, I guess. Is Slide something
> like a document repository that can be connected to a J2EE container
> just like an RDBMS? Or is it an integrated part of a J2EE container
> resp. web container (like Tomcat)?
>
I think attacking the full container integration is too big a task if we want a
2.0 release early next year.
And in any case a J2EE / Servlet Container is 'well specified'. There is no
specification, as far as I am aware, for a WEBDAV based J2EE container. It
sounds neat, but big and complicated. I think staying focused is important if
we want to make a release...
Richie
> Oliver
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-dev-help@jakarta.apache.org
>
>
>
---------------------------
This mail sent through the
ungerground webmail system
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: Features of Slide 2.0 release
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Oliver Zeigermann wrote:
> 1.) What features not yet implemented should go into the Slide 2.0 release?
There has been a patch JTA patch proposed by Grant Gongaware some time
ago. This made the transaction manager implmentation configurable to use
the containers instead of Slides integratied TM. It also included some
patches moving certain read actions inside transactions.
While these patches cetainly are valuable (ah, need to check them and
add Grant to the contributors list) the concept of using external TMs is
to be discussed. The idea of connectors to plug Slide into J2EE
containers come up more than once as well. However, this is a bit tricky
as Slide needs a web container (not a full J2EE container) to run in the
first place. This would mean you might have two containers running.
Isn't that weird?
This really is a philosophical question, I guess. Is Slide something
like a document repository that can be connected to a J2EE container
just like an RDBMS? Or is it an integrated part of a J2EE container
resp. web container (like Tomcat)?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org