On Wednesday 12 November 2003 18:26, Berin Loritsch wrote:
> Niclas Hedhman wrote:
> > On Friday 07 November 2003 17:04, Berin Loritsch wrote:
> >>The solution I propose would allow and foster the creation of several
> >>component repositories, but provide one index so that folks know where to
> >>look for components that they may want to use.
> >
> > An index is not a repository. People can look up an index, interpret the
> > content, move on to N locations, interpret the "local language", figure
> > out which component can do what is needed,  find the download area, and
> > manually insert them into a development effort.
> >
> > How about a tool doing this?? Not that easy...
>
> That is what I was getting at.

Sorry, it wasn't obvious, sounded more like a "web site with pointers"...

> And the fact that an index is not a repository was the exact point I wanted
> to make.  I think having a one size fits all repository is destined to
> fail. Having an index to support the infrastructure of finding components
> that would be needed from multiple repositories would allow for several
> repositories that are *focused* on a particular problem space.  That would
> facilitate islands of expertise which can be leveraged.

OK, you have a lot of work set out in front of you ;o) (or us...)

Since I am concentrate my efforts on the IDE use-case, my conclusion is 
roughly like this;

The Eclipse plug-in can (and probably should be) completely 
repository/directory agnostic. It only understand a fairly simple event-based 
interface, and depend on implementations to connect to my "simple repo" 
today, and to the hyper-duper searchable one tomorrow

So, now I just need to nail down the use-case.


> We would need to look at options for "self management".  Have it all hosted
> as an Avalon project using Merlin to run the index server, and it would
> really rock.

Sure would, especially if Merlin is "componentized" down to the main() method 
(or beyond), it can update itself ;o).

Does anyone know anything about the P2P model. Would that be feasible and 
desirable?

Overall, I agree with you on the technical vision, just that I believe it is a 
fairly large step to make (I like babysteps), and just freak out when I see 
the amount of work required to make it a reality.


Niclas

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to