Slide Stores

[Unico Hommes <Un...@hippo.nl>]

Hi !

I have a question about the slide stores. I took a look at some of them. I
would like to use MySql for the descriptor storage etc. but I noticed that
it said in the source of the MySqlDescriptorsStore that code was only to be
used with mysql 3.22 or earlier. Can anybody tell me why this is ? What
would it take to write a MySqlDescriptorsStore for later versions, could I
stick with the default JDBCDescriptorsStore. Also, MySqlDescriptorsStore
extends AbstractSimpleService wich means that only one transaction context
can exist at one time. Does this mean that concurring transactions are
qeued, or does slide instantiate multiple stores. Would a real world
application that must scale for say, 50 concurrent users, have to use
multi-transaction capable stores, such as one extending AbstractService ?

Thanks,

Unico Hommes


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: FileContentStore and revision

[Dirk Verbeeck <di...@pandora.be>]

Hi Kevin

The slide engine has versioning support but the WebDAV interface
doesn't.
That Delta V support is on our wish list but that wish hasn't been
granted yet ;-)
So there isn't a magic config option that you can enable.

Dirk

Kevin O'Neill wrote:
> 
> Hey all, I'm wondering if someone could shed a little light for me.
> 
> I've installed Slide 1.0.16. The standalone server runs straight out of
> the box (very happy). I have one question though, is the content store
> supposed to be configured for versioning. I've looked at the
> configuration files and they seem to indicate it is, but when I update a
> file via WebDAV the content on the server is overwritten rather than and
> additional version being created.
> 
> What stupid nubie thing have I done :)?
> 
> k.
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

FileContentStore and revision

[Kevin O'Neill <ke...@rocketred.com>]

Hey all, I'm wondering if someone could shed a little light for me.

I've installed Slide 1.0.16. The standalone server runs straight out of
the box (very happy). I have one question though, is the content store
supposed to be configured for versioning. I've looked at the
configuration files and they seem to indicate it is, but when I update a
file via WebDAV the content on the server is overwritten rather than and
additional version being created.

What stupid nubie thing have I done :)?

k.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Slide Stores

[Dan Diephouse <di...@eastnode.com>]

That is correct.  With Mysql 3.23 and above (Or maybe it was version 
3.22.23 and above, I don't remember) you need to use the 
JDBCDescriptorStore.  Before that mysql was broken because transactions 
didn't work, so MySQLDescriptor store was developed.

- Dan Diephouse

Jean-Philippe Courson wrote:

> Unico Hommes wrote:
>
>>
>> Hi !
>>
>> I have a question about the slide stores. I took a look at some of 
>> them. I
>> would like to use MySql for the descriptor storage etc. but I noticed 
>> that
>> it said in the source of the MySqlDescriptorsStore that code was only 
>> to be
>> used with mysql 3.22 or earlier. Can anybody tell me why this is ?
>
>
>
> I think it's because MySQL correctly supports transactions only from 
> this version.
>
> JP





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Slide Stores

[Jean-Philippe Courson <co...@noos.fr>]

Unico Hommes wrote:

> 
> Hi !
> 
> I have a question about the slide stores. I took a look at some of them. I
> would like to use MySql for the descriptor storage etc. but I noticed that
> it said in the source of the MySqlDescriptorsStore that code was only to be
> used with mysql 3.22 or earlier. Can anybody tell me why this is ?


I think it's because MySQL correctly supports transactions only from 
this version.

JP




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>