On Mon, Feb 25, 2008 at 4:17 PM, Jean-Sebastien Delfino <
[EMAIL PROTECTED]> wrote:

>  >> Jean-Sebastien Delfino wrote:
> >> Looks good to me, building on your initial list I added a few more
> items
> >> and tried to organize them in three categories:
> >>
> >> A) Contribution workspace (containing installed contributions):
> >> - Contribution model representing a contribution
> >> - Reader for the contribution model
> >> - Workspace model representing a collection of contributions
> >> - Reader/writer for the workspace model
> >> - HTTP based service for accessing the workspace
> >> - Web browser client for the workspace service
> >> - Command line client for the workspace service
> >> - Validator for contributions in a workspace
> >>
> >>
> > ant elder wrote:
> > Do you have you heart set on calling this a workspace or are you open to
> > calling it something else like a repository?
> >
>
> I think that they are two different concepts, here are two analogies:
>
> - We in Tuscany assemble our distro out of artifacts from multiple Maven
> repositories.
>
> - An application developer (for example using Eclipse) can connect
> Eclipse workspace to multiple SVN repositories.
>
> What I'm looking after here is similar to the above 'distro' or 'Eclipse
> workspace', basically an assembly of contributions, artifacts of various
> kinds, that I can load in a 'workspace', resolve, validate and run,
> different from the repository or repositories that I get the artifacts
> from.
> --
> Jean-Sebastien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

To me repository (in my mind somewhere to store things) describes a much
less active entity compared to the workspace which has to do a lot of work
to load and assimilate information from multiple contributions. I'm not sure
about workspace either but to me it's better than repository and it's not
domain which has caused us all kinds of problems.

My 2c

Simon

Reply via email to