Yes, my email is [EMAIL PROTECTED]
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Perritano Sent: Wednesday, May 21, 2008 11:25 AM To: [email protected] Subject: [SAIL-Dev] Re: working on webdav access to jackrabbit repo David, can you email me yr google email address and i will add you as a member. -Tony On [May 21], at 8:21 AM, Rokham Sadeghnezhadfard wrote: Hi David and Tony, After our meeting in Berkley with the European guys we have come up with a new API called Roolo. Roolo uses our previously defined API though. Can you please check-out the roolo project and add your changes to that api instead of the old cms project? We're not going to use the cms project since it's code-base has been merged with the roolo project. You can check out the roolo projects from https://roolo.googlecode.com/svn ps. Tony can you please make sure that David has access to the roolo project? Thanks On Wed, May 21, 2008 at 9:59 AM, Stephen Bannasch <[EMAIL PROTECTED]> wrote: At 9:05 AM -0700 5/20/08, Hiroki Terashima wrote: > David, do you have documentation on your work with webdav access to jackrabbit? Can you coordinate your work with Scott's somehow? > > Scott, I'm guessing here that we (Concord, Toronto, Berkeley) all want the same thing (adding webdav access to jackrabbit repo and using jackrabbit in general for CMS). Would it not behoove us to collaborate, to reduce redundant code? Scott's doing exactly what we discussed at last Friday's SAIL dev meeting. He's: * Continuing his work on building a prototype of an OTDatabase implementation that uses a remote JCR-based repository for OTrunk that deeply models the object relationships that OTrunk makes possible. * Architecting the JCR modeling of OTrunk so that all possible OTrunk layers of Object data are represented and efficient queries can be made on and among these different layers. * Evaluating both JackRabbit and JCR in regard to these requirements: ** query performance with a large repository of activity, learner, and techer data. ** semi-realtime collaborative access ** replication of repositories It's important to remember that this is an investigation into JackRabbit and JCR. If the results of the investigation show problems that are impractical to solve we'll need to find another solution. * Posting messages to the email list. * Writing wiki pages about his work. This is much more involved work than just "webdav access to jackrabbit repo and using jackrabbit in general for CMS" -- most of it is integration at a much deeper level and is complementary work. One small but essential part for the prototype work is the webdav access. This overlaps a great deal, but David hasn't yet posted a description of his work. So how exactly how is this not collaborating? -- Rokham No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.21/1458 - Release Date: 5/21/2008 7:21 AM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
