[aosd-discuss] Aspects and security (was: Non academic ideas on AOSD)

[leeca at pnambic.com]

AW: [aosd-discuss] Aspects and security (was: Non academic ideas on
AOSD)I've used the annotation "Singleton" to indicate that a module is NOT
designed with collaboration in mind.  Like Arno and Juri, this is rare
occurance.  (Largely due to laziness on my part:-).  This is one of three
basic integration modes that seem clear in evolved code.  (The other two are
Fusion and Dispatch).

It's rarely a big deal to change a Singleton unit to a Fusion unit, and it's
only a little more effort to change it to a Dispatch unit.  However, marking
it Singleton forces me to make a concouses decision about the interactions
of the contributed software units.

This annotation could also be used to mark software units that refuse other
contributions, such as securtiy or password interfaces.
---
http://www.pnambic.com/leeca
... The real cycle you're working on is a cycle called 'yourself'.
  From: Arno.Schmidmeier at sirius-eos.com
  Subject: AW: [aosd-discuss] Aspects and security (was: Non academic ideas
on AOSD)

  ...
  At least security is a strong argument for a "do not weave code here"
statement and the correct support in AOP languages, bytecode and future VMs.

  ... Please note also:
  This kind of statement will most likely be used very, very rarely.
  I expect less then 5 classes, in one of my projects, which contained more
than 4000 classes.



  kind regards
    Arno

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://server2.hostvalu.com/pipermail/discuss_aosd.net/attachments/20021017/765bf7a3/attachment.htm