History for MVCAndInterfaces

??changed:
-
MVC and Interfaces

  We at Digital Creations have put some time lately into attacking the 
  problem of: "Why haven't we documented our api?"  This is evolving 
  into a proposal for documented interfaces in Zope.

  As we work on this, we realize that our current api has accumulated, 
  and we never spent the time to run it through a *process*.

  Now we have backwards-compatability issues, of course, meaning we can't 
  just craft a new api.  Or can we?

  With MVC, we can start writing a new api, one without 'manage_' in 
  front of everything. :^)  We make this the *model*, then hook the 
  "Classic Zope Management Interface" up to be a view on this "good" 
  api.

  Other views, such as a Mozilla view, an xml-rpc view, etc. could 
  point to this model.

----------  

  My thoughts exactly. I still have to work out how to make sure the 
  published object will still listen to the same URLs though. -- MartijnPieters