On 18 Nov 2003, at 06:41, Martin Holz wrote:
Oliver Zeigermann [EMAIL PROTECTED] 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
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
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
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
-Original Message-
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
Sent: Freitag, 21. November 2003 09:33
To: Slide Developers Mailing List
Subject: Re: Features of Slide 2.0 release
My try of a summary of the links:
- Sometimes more than one request shall be processed atomically
Martin Holz wrote:
Oliver Zeigermann [EMAIL PROTECTED] 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
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,
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
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
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: [EMAIL PROTECTED]
For additional
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
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.
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
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
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
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 [EMAIL PROTECTED]
Am Dienstag, 18. November 2003 15:41 schrieb Martin Holz:
Oliver Zeigermann [EMAIL PROTECTED] 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
Martin Holz wrote:
Oliver Zeigermann [EMAIL PROTECTED] 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
18 matches
Mail list logo
