components, parcels, services, application frameworks

• components conversations on irc
  • In particular, hazmat mentioned not reinventing the wheel:
    • pyprotocols (looks like java interfaces) http://www.python.org/peps/pep-0246.html
    • z3 component architecture (if I remember correctly, something like an enterprise component architecture, not unlike j2ee)
    • twisted interfaces
  • how do pyprotocols square with python's notion of consenting adults?

• Should we be thinking about Chandler as an application server?
• should the parcel framework become more of a real component framework? what are the advantages?

• more conversation with hazmat on irc
  • z3 interfaces: http://cvs.zope.org/Zope3/src/zope/interface/README.txt?rev=1.1&content-type=text/vnd.viewcvs-markup
  • z3 tutorial: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ProgrammerTutorial

• framing goals of parcel framework, components, services:
  • parcel framework as a packaging/distribution mechanism
  • component framework
    • interfaces to components
    • adaptation protocol (pyprotocols)
    • lookup protocol
  • define the common services

• Aleks Totic pitched this to me a while back (while I was underwater or asleep or something): OSGi, as used by Eclipse
  • http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg00038.html (requires id and password from eclipse)

-- KatieCappsParlante - 30 Apr 2004