Re[2]: [equinox-dev] Bundle directories

[Peter Kriens <Peter.Kriens@xxxxxxxx>]

RSH> This is essentially OBR's approach; however, there is no "detection"...
I did not mean that the discovery should "detect", but once connected
to the OSGi repository, you must be able to learn about all other
repositories. I.e. the repositories can be a connected in a mesh.

RSH> I would still argue for no server at all, since it raises the cost of entry.
I like the idea, but the disadvantage is that it does not scale. We
are currently discussing to make an OSGi hardware evaluation kit which we'd
like to make as small as possible. It would be nice if the client
could be very small. Then again, maybe we can have a 2 pronged
approach where that class of device has a management system which
preprocesses. (One of the recruited evangelists is interested
in making open source with the support of his company, so that might
be combined).

OBR is very close in what I envisioned (with what I understand of the
capabilities and reqs model). Though authentication and maybe local
cache needs to be adressed for Jeff's extra needs.

Richard, can you give a short intro to how OBR will work with the
capabilities and requirements? I.e. how does it work with fragments,
optional requirements, require bundle, etc.?

Kind regards,

     Peter Kriens

->> richard
RSH> _______________________________________________
RSH> equinox-dev mailing list
RSH> equinox-dev@xxxxxxxxxxx
RSH> https://dev.eclipse.org/mailman/listinfo/equinox-dev


-- 
Peter Kriens                              Mob +33633746480
9C, Avenue St. Drézéry                    Tel +33467542167
34160 Beaulieu, France                    Tel +15123514821
                                          Tel +33870447986
AOL,Yahoo, Skype pkriens                  ICQ 255570717