RE: Slide API
The one problem I see with using either the Slide client API or WVCM is user authentication. The user must supply a username and password to authenticate. So if you are writing a portlet to display the contents of the content store you must have access to the user's password. In my environment this is not acceptable. I looked at the Slide server API as a way to get around this problem. What might work real well is to support something like SAML assertions as a method of authentication and identity passing. Just my two cents. Regards, James James Chamberlain General Dynamics - Advanced Information Systems Prototype Pathway - Collaborative Information Environment U.S. Joint Forces Command [EMAIL PROTECTED] -Original Message- From: Michael Oliver [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:32 AM To: 'Slide Users Mailing List' Subject: RE: Slide API I would concur with Daniel, any performance downside is trivial and in my experience any gains would not be worth the effort and I would doubt would be observable by a user. The big advantage is load balancing so you can use parallel processing in multiple VM's if you use the WebDAV interface whereas you cannot if going directly to the Server API and as Daniel points out you can't do everything with the Server API as yet anyway. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 Lord, I love you and I need you, come into my heart, and bless me, my family, my home, and my friends, in Jesus' name. Amen -Original Message- From: Daniel Florey [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 5:22 AM To: Slide Users Mailing List Subject: Re: Slide API Hi Marc, my strong advice would be to stay with WVCM or switch to webdavclient-lib. If you are using the Slide api directly, you'll run into trouble. At the moment, some of the repository logic (binding, versioning etc.) is unfortunately coded into the webdav layer. So if you create revisions using the slide api, you cannot access that via deltav lateron. We are currently doing some progress on speeding up the Slide server in general, so: stay with wvcm. Regards , Daniel [EMAIL PROTECTED] wrote: >Hi, > >Currently we are using the WVCM api to access the webdav server. As we looked at the architecture overview documentation of slide, we saw that it is possible for a java application in the same JVM to access directly the slide server api. > >This is our case, our business logic for lifecycle management runs inside the same web server. We would like to know if it would be possible to use directly the slide server api and what would be the consequence (improve of performance, functionality available). > > >Regards > >Marc Lefevre > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
setLastModified Issue while copying / transferring file [There must be something that I am missing]
I have been working with slide and getting a good understanding
so far. I have almost deployed SLIDE solution on production and now
struck with a situation {as described below}. Please help, appreciate
much.
ISSUE:
When any file(s) is copied / transferred from local HDD /
network drive to a SLIDE folder, the file(s) being copied looses its
ORIGINAL 'Date Modified' and assumes the current date (the date when
copy occurred). This is a major issue for us. It is highly desirable
the file(s) retain its original 'Date Modified' value.
I took a look at PUTmethod.java and notice the setLastModified
is assigned new Date, instead of the object's original date.
Is there anything I can do to retain the files original date
value! Any direction, configuration suggestion, code modification please
suggest.
Thank you very much for all your time and efforts.
I use SLIDE 2.0, Tomcat 5.x on RH Linux 9.0.
Swam Palani
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Slide API
I would concur with Daniel, any performance downside is trivial and in my experience any gains would not be worth the effort and I would doubt would be observable by a user. The big advantage is load balancing so you can use parallel processing in multiple VM's if you use the WebDAV interface whereas you cannot if going directly to the Server API and as Daniel points out you can't do everything with the Server API as yet anyway. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 Lord, I love you and I need you, come into my heart, and bless me, my family, my home, and my friends, in Jesus' name. Amen -Original Message- From: Daniel Florey [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 5:22 AM To: Slide Users Mailing List Subject: Re: Slide API Hi Marc, my strong advice would be to stay with WVCM or switch to webdavclient-lib. If you are using the Slide api directly, you'll run into trouble. At the moment, some of the repository logic (binding, versioning etc.) is unfortunately coded into the webdav layer. So if you create revisions using the slide api, you cannot access that via deltav lateron. We are currently doing some progress on speeding up the Slide server in general, so: stay with wvcm. Regards , Daniel [EMAIL PROTECTED] wrote: >Hi, > >Currently we are using the WVCM api to access the webdav server. As we looked at the architecture overview documentation of slide, we saw that it is possible for a java application in the same JVM to access directly the slide server api. > >This is our case, our business logic for lifecycle management runs inside the same web server. We would like to know if it would be possible to use directly the slide server api and what would be the consequence (improve of performance, functionality available). > > >Regards > >Marc Lefevre > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 170 available for Public Review
Hi Terence, this is exactly what WebDAV tries to be: A specification that is not limited to a special programming language. It's a protocol, but it can be seen it as an api (method names + (header/body)parameters ) So I'd prefer an API that brings WebDAV to the java world. Some kind of combination between Slide webdavclient and JSR-147. Regards, Daniekl Terence Kearns wrote: Davide Savazzi wrote: http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) just a comment on the JSR in general. It's too bad such a specification doesn't supercede a given technology (Java) as does the DOM API for instance. Then developers from other technologies (like .NET, PHP and others) could benefit in the same way all XML developers have benefited from the DOM API. You could say the same for many Java specifications I guess but this one is so inherently techno heterogeneous. It seems to me that JSR170 is like a macroscopic version of DOM -- where the repository in the case of DOM was restricted to XML packets and the XML infoset protocol. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide API
Hi Marc, my strong advice would be to stay with WVCM or switch to webdavclient-lib. If you are using the Slide api directly, you'll run into trouble. At the moment, some of the repository logic (binding, versioning etc.) is unfortunately coded into the webdav layer. So if you create revisions using the slide api, you cannot access that via deltav lateron. We are currently doing some progress on speeding up the Slide server in general, so: stay with wvcm. Regards , Daniel [EMAIL PROTECTED] wrote: Hi, Currently we are using the WVCM api to access the webdav server. As we looked at the architecture overview documentation of slide, we saw that it is possible for a java application in the same JVM to access directly the slide server api. This is our case, our business logic for lifecycle management runs inside the same web server. We would like to know if it would be possible to use directly the slide server api and what would be the consequence (improve of performance, functionality available). Regards Marc Lefevre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse webdav support in M9
Hi folks, a was wondering if anybody around here is using the eclipse WebDAV-plugin. The current implementation is broken in M9 as far as I can tell. A colleague of mine sent some patches to fix the plugin, so that it finally works with Slide. Unfortunatley, the eclipse guys don't have much time and the WebDAV-plugin seems not to have the highest prio, so they are currently not planning to fix this for 3.0. This are the bugreports regarding Slide: https://bugs.eclipse.org/bugs/show_bug.cgi?id=58240 https://bugs.eclipse.org/bugs/show_bug.cgi?id=58237 https://bugs.eclipse.org/bugs/show_bug.cgi?id=61582 Is any eclipse guru around here, who can make the working WebDAV-support happen? Regards, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
Oliver Zeigermann wrote: ... now that I am at it ... looking at how content is stored ... What are the limitation of the "bytea" field? Anything better available? The other alternative with PostgreSQL is the legacy large object interface. But it has a different programming model that will require changes in the adapter class. The advantage is that it supports up to 2GB whereas bytea can only currently handle 1GB. However, large objects are considered obsolete, so BYTEA is the right choice at the moment. If there's a need for larger files, it's likely that PostgreSQL developers enhance BYTEA or add another compatible BLOB type. Carlos Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: ... and by the way ... also quoting from the link concerning performance of char, varchar and text Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. Why not simply replace all varchar types by text and be fine forever? Carlos? What do you say? Other Postgres experts? I agree. I usually use TEXT and don't bother about limits on the database side. Just like in this case, very often you exceed your limits and have to change the schema. Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
... now that I am at it ... looking at how content is stored ... What are the limitation of the "bytea" field? Anything better available? Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: ... and by the way ... also quoting from the link concerning performance of char, varchar and text Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. Why not simply replace all varchar types by text and be fine forever? Carlos? What do you say? Other Postgres experts? I agree. I usually use TEXT and don't bother about limits on the database side. Just like in this case, very often you exceed your limits and have to change the schema. Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
OK, I will change all varchar to text. If someone complains I will revert it ASAP. Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: ... and by the way ... also quoting from the link concerning performance of char, varchar and text Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. Why not simply replace all varchar types by text and be fine forever? Carlos? What do you say? Other Postgres experts? I agree. I usually use TEXT and don't bother about limits on the database side. Just like in this case, very often you exceed your limits and have to change the schema. Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
Oliver Zeigermann wrote: ... and by the way ... also quoting from the link concerning performance of char, varchar and text Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. Why not simply replace all varchar types by text and be fine forever? Carlos? What do you say? Other Postgres experts? I agree. I usually use TEXT and don't bother about limits on the database side. Just like in this case, very often you exceed your limits and have to change the schema. Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
Ah, I see. I will change the type to text in the CVS then. This will be part of the next release. Concerning UTF-8 support (important for Slide) I quote from the link Carlos provided: The type of data stored in these fields depends on the encoding specified during database creation. To create a database which stores Unicode strings (reportedly stored as UTF-8) create the database with either: createdb -E UNICODE mydatabase or CREATE DATABASE mydatabase WITH ENCODING = 'UNICODE' Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
... and by the way ... also quoting from the link concerning performance of char, varchar and text Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. Why not simply replace all varchar types by text and be fine forever? Carlos? What do you say? Other Postgres experts? Cheers, Oliver Carlos Villegas wrote: Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to creat a new user in Slide
Hi Simone, I forgot to restart the server till this morning... :$, it didn't take the modify in tomcat-user.xml and it works much better now.^^ Thank you^^ Lea Simone Gianni <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]: > Hi Lea, > please have a look at previous posts in this mailing lists, search for > subject "how can i create new user in slide", in dates ranging from 21 > to 24 of May. In that thread there are pointers to documentation and > some explanations of how the slide realm must be used to have the user > logging in. > > Ciao, > Simone Gianni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
Oliver Zeigermann wrote: This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Yes, "TEXT" is supported in PostgreSQL: http://www.postgresql.org/docs/7.4/interactive/datatype-character.html Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkin problem with Slide 2.0
This was fixed for *MySQL* only, *Postgres* still needs the fix. Simple solution would be to increase the maximum size of the property. Maybe there is something similar to "text" in MySQL in Postgres as well? Postgres experts around? Oliver Ritu Kedia wrote: This should be because of the restriction of 255 chars on the "Property_Value" column of "Properties" table. With 255 characters you can go up to only 5 versions. I think this has been fixed in 2.1 M1. Regards, Ritu -Original Message- From: Shuji Aono [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:17 AM To: [EMAIL PROTECTED] Subject: Checkin problem with Slide 2.0 Hi, I have a problem in check-in. I'm running version 2.0 of slide server and client library. An exception of "value too long for type character varying(255) " occurs that RDBMS continues repeating check-out and check-in with the same file in case of Postgres. The check-out and the check-in repeated themselves six times. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Checkin problem with Slide 2.0
This should be because of the restriction of 255 chars on the "Property_Value" column of "Properties" table. With 255 characters you can go up to only 5 versions. I think this has been fixed in 2.1 M1. Regards, Ritu -Original Message- From: Shuji Aono [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:17 AM To: [EMAIL PROTECTED] Subject: Checkin problem with Slide 2.0 Hi, I have a problem in check-in. I'm running version 2.0 of slide server and client library. An exception of "value too long for type character varying(255) " occurs that RDBMS continues repeating check-out and check-in with the same file in case of Postgres. The check-out and the check-in repeated themselves six times. -- Shuji Aono <[EMAIL PROTECTED]> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
