Putting back at least one response from the user-standpoint versus dev -- thank goodness for the seperation and redesign! :-D
Slide has worked great to-date, but as new requirements and new needs came up, it has started to get a little ugly, and as anyone knows, only a few people would want to jump into a project if the learning curve is too high. Just a couple of thoughts as you consider the redesign - *ConfigStore - Possibly moving the generic configuration of all the stores (each with specific pointers/parameters/etc - like the URI and serving-side security/ACL per store) into a single ConfigStore that is centric to the SlideServer and not have each-store-store-its-own-config. Would be easier for future management extensions. *Allow easy integration of existing repositories - I like that. One use-case I've been trying to use is if using the Slide TxXmlDescriptor and TxFileStore Stores to collect items and metadata, then taking a snapshot/state and burn it to CD, and then trying to re-integrate it back into the Slide server (which doesn't work as the Tx** won't work with read-only media, and is kinda a pain working with the domain.xml to re-integrate it back). Again, this is just a user-perspective, but looking forward to the Slide 3.0 redesign! -D --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
