Just a thought. Would it be possible to use Alon's new simple file stores for the node/content store and a jdbc store for the revisiondescriptors? As far as Slide could tell the files would be writeable (I suppose you could set an inheritted write-content denied ACE) but Slide handles non-writeable stores fairly well (JNDI store for instance).
If I understand the problem description correctly (I'm on codine right now so no promises) you might want one jdbc-only store for your business metadata and one simple file store/jdbc metadata store for each data location (CD/DVD/etc). All you'd really end up storing for the metadata on the files would be the storage key (or whatever you called it). -James On Thu, 2004-09-30 at 07:29, Oliver Zeigermann wrote: > I do not think this will work without any modification in the Slide > stores, but they should be minor and doable. > > Oliver > > Darren Hartford schrieb: > > > Hi Oliver, > > I'm looking for a single interface to use. The end result is I'm looking for an > > 'image repository' that supports Hierarchial Storage Management (HSM) where an > > image could be stored on local drive, NAS, CD/DVD rom, remote Jukebox, or other > > storage media in a scenario where a single image may be stored in multiple > > locations. > > > > Second thing is the 'metadata repository' to do searches against to find the > > correct image(s). In this context, metadata/index data/search data represents > > business information and not image metadata (names, codes, dates, etc). The > > business information is stored in XML, and searches would be done with > > XPATH/XQuery. > > > > Tieing the two repositories together is still in question, but that is where > > integration comes in (search XML, return X-many results, in the results mention a > > image identifier, search image repostiories for instance(s) of that image > > identifier across the HSM, retrieve image). > > > > Since Slide supports both file storage and XML DB storage, it makes sense to use > > this *one* tool for both of the above repositories. Since I would like to support > > HSM and allow CD/DVD/Jukebox access to images that no longer require high-speed > > access, the question brought up is if Slide can access and manage a 'store' > > located on CD/DVD/Jukebox to have one interface for retrieving all images (for > > application integration). > > > > End result - looking to build a Document Management Repository. One of the > > Slide-Architecture diagrams talks about using Slide to store information into a > > Doucment Management Repository, but I'm rather looking to create one. > > > > p.s. thanks for the very timely response! > > > > -D > > > > > > > > > >>-----Original Message----- > >>From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > >>Sent: Thursday, September 30, 2004 9:57 AM > >>To: Slide Users Mailing List > >>Subject: Re: [newbie] Slide with read-only support? > >> > >> > >>Hi Darren, > >> > >>just wondering: If you want read only access than why not use > >>a a simple > >>HTTP server? Or did I get you wrong? > >> > >>Oliver > >> > >>Darren Hartford schrieb: > >> > >>>Hey all, > >>>Very new to Slide, and coming in from the J2EE side looking > >> > >>for a solution to support transactional file storage (with > >>possible integration with Enterprise Media Beans (EMB) for > >>actual presentation). > >> > >>>One of my concerns before getting too far in was simply > >> > >>this - since Slide is based (partly) on WebDAV, from what I > >>understand WebDAV needs to have write-access for the files > >>under its management. The question is, can you add a storage > >>location such as a CD/DVD/Jukebox to a Slide repository for > >>read-only access to the files stored on that type of media? > >> > >>>thanks, > >>>-D > >>> > >>> > >> > >>--------------------------------------------------------------------- > >> > >>>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]
