[maynstall-dev] Update site processor

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Hello,

If I remember correctly, mayinstall processes update sites to generate its
metadata.
In p2 we now have a mechanism to produce metadata on the fly when we are
installing from update sites. However this is pretty distasteful because we
have to jump through hoops to generate the complete IU for a bundle while
we are actually installing it.
So here is the question, based on your experience, do you believe an
approach where the client would go and get the manifest from every jar of
the update site feasible / scalable, etc.?

Thx in advance for your input,

PaScaL