> I'd rather see a viewcontroller go into one of the common projects (if one is > appropriate) and then have Orchestra depend on that.
that would be a good idea; I started thinking about REST, to have the viewController call some "callbacks". I was inspired about a talk at ApacheCon US on the S2 RESTplugin + codebehind-plugin (which is a view-controller-technology) > > I've always felt that a view-controller is not really a core part of > Orchestra's functionality. And a view-controller is useful to many projects > that may not want conversation support. yup, see above > > Regards, > > Simon > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
