**** Some of the problems with the adapters in the platform in the white paper - Darin would like to do some improvements in the API. Do we want to use the JFace virtual viewers and change the way the content adapters work?

+

**** The document claims that you can only have 1 adapter per type. That's true, you can have 1 adapter per kind of implementation instance, but more than one adapter per interface.

+

**** Question: The DSF model feels like a reimplementation of the standard debug model in the platform. Pawel: We want to replicate some of what the standard debug model does, but we want to make it asynchronous.

*** Last mtg AI: '''Darin will update us at the next meeting.''' Update?

*** Last mtg AI: '''Darin will update us at the next meeting.''' Update?

−

*** Need to staff the work as patches in the DD project?

+

**** No proposed item for pin/clone support in the plan. So it's not committed, but Darin will help others who want to prototype in the DD project. '''Darin also needs to talk to Pete and email the group.'''

+

**** Need to staff the work as patches in the DD project? Possibly, waiting on Darin.

Some of the problems with the adapters in the platform in the white paper - Darin would like to do some improvements in the API. Do we want to use the JFace virtual viewers and change the way the content adapters work?

The document claims that you can only have 1 adapter per type. That's true, you can have 1 adapter per kind of implementation instance, but more than one adapter per interface.

Question: The DSF model feels like a reimplementation of the standard debug model in the platform. Pawel: We want to replicate some of what the standard debug model does, but we want to make it asynchronous.