Hi Sascha - thanks for the reply! So if I understand right images will not be stored on the app servers but on another server that is running the jackrabbit storage services? After these changes are merged only one copy of a product image will need to be saved in jackrabbit and now removes the need to sync image files between app servers if you are running a load balanced or cluster setup??
Thanks Sam On 11 Nov 2011, at 15:27, Sascha Rodekamp wrote: > Hi Sam, > nope. Content information (images, text, files ...) will be stored in a > content repository beside our normal (SQL) Database. > > A content repository is an information management system that provides > various services for storing, accessing, and managing content. In addition > to a hierarchically structured storage, common services of a content > repository are versioning, access control, full text searching, and event > monitoring (see http://jackrabbit.apache.org/frequently-asked-questions.html > ). > > In our current configuration of Jackrabbit we have to differentiate between > file and other content. > Because files are normally larger than normal text i adviced Jackrabbit to > store files directly on the file system and create a reference in the > repository (that have performance reasons). On the other side text content > is directly stored in the repository nodes (each item in a repository is > called node, a node have different attributes which contains the content > and metadata). > > Hope that answered your question?! > Regards > Sascha > > > 2011/11/11 Sam Hamilton <s...@sh81.com> > >> Hi Sascha, >> >> Please excuse my ignorance but does this branch mean that content >> information such as images will be stored in the database base instead of >> on the app servers? >> >> Thanks >> Sam >> >> >> >> On 8 Nov 2011, at 21:55, Sascha Rodekamp wrote: >> >>> Hi Erwan, >>> >>> in my opinion step one is done. >>> Includes: An abstract and completely independent framework module to >> attach >>> any JCR implementations you want to OFBiz, Jackrabbit is the default >>> implementation. >>> >>> The basic CRUD functions, versioning and support for different languages >>> works and looks stable :-). >>> >>> What is missing: Someone who reviews the architecture :-), have a short >>> look to my code and gives a feedback. >>> >>> From my point view we could back merge without any problems because there >>> are now cross dependencies to other modules. >>> >>> Cheers >>> Sascha >>> >>> >>> >>> >>> 2011/11/8 Erwan de FERRIERES <erwan.deferrie...@gmail.com> >>> >>>> Hi Sascha, >>>> >>>> what is missing for merging trunk and jackrabbit branch ? >>>> >>>> Cheers, >>>> >>>> >>>> -- >>>> Erwan de FERRIERES >>>> >>> >>> >>> >>> -- >>> >>> Sascha Rodekamp >>> Visit the new german OFBiz Blog: http://www.ofbiz.biz >>> Lynx-Consulting GmbH >>> Johanniskirchplatz 6 >>> D-33615 Bielefeld >>> http://www.lynx.de >> >> > > > -- > > Sascha Rodekamp > Visit the new german OFBiz Blog: http://www.ofbiz.biz > Lynx-Consulting GmbH > Johanniskirchplatz 6 > D-33615 Bielefeld > http://www.lynx.de
smime.p7s
Description: S/MIME cryptographic signature
