Paul Hammant wrote: > > OK, Team A ship a sar file with X Y and Z as blocks. Fred (an > administrator type person) for a compant decides that he wants to deploy > with Y2 instead of Y (a better implementation for his setup), he puts on > his "re-assembler" hat and replaces the block (bar file) in the sar > file, then deploys it as ususal. "Assembler" was one of the original > promises of the pluggable component design of Avalon..... it's juste > never been discussed as a role.
Ok, I do (and did ;-) understand what an assembler has to do. We are frequently swapping blocks within .sar applications, for example to roll back to an older version, if the new version misbehaves. This is a very handy feature of Avalon and everyone loves it. What I was wondering, however, is whether an Avalon-agnostic person, like a system administrator, would be allowed or required to do this. I think no. The decision to use Avalon is made by the developers, the admins want to know how to stop and start it, but not how to fix something internal to an Avalon installation or a .sar application. Therefore I think the role "Assembler" can have the same rights and duties as the role "Developer". The decision which version of a server-side software to deploy is ultimately made by the developer - I haven't seen anything else, at least. Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
