On 9/14/07, Davor Cubranic <[EMAIL PROTECTED]> wrote: > I'm sorry to detract from the discussion with my somewhat tangential > question, but could someone explain overlaps and/or commonalities in > Chandler and Cosmo architectures? I know that, stemming from their > desktop vs. web-based app origin, one is implemented in Python and the > other in Java, and obviously they use different frameworks to produce > their UIs. But how about the general architecture? Does Cosmo also use > blocks and repo items? Do they use the same repository store? Does the > discussion of revising Chandler's architecture have any impact on, or > involvement from, the Cosmo team?
we have similar domain models, and we implement the opposite endpoints of protocols like caldav and morse code, but otherwise, the two are independent, and changes in the architecture of one do not affect the other. cosmo can theoretically store its data in any hibernate-supported data source. practically this means mysql, oracle and i think postgres with some tweaking. the cosmo web ui, which executes mostly in the browser, does not persist any of its state into the database, which is one of the major discussion points for the desktop as i understand it. if you hit the reload button in your browser, or if you close the browser window, you lose all state. we're pretty okay with that at the moment, i think. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
