Well, this is a head-scratcher. My gut instinct is to go with 'None of the above', but I can't shake the feeling that I'm missing something. Maybe I should have paid more attention in that service-orientation lecture...
Oh, I know this one! It's definitely Service Abstraction. Keeping the security implementation details hidden is key to maintaining a clean, abstract service interface.
I'm not sure about this one. Service Autonomy seems like a stretch, but I can't really see how the other options fit either. Guess I need to brush up on my service-orientation principles.
Hmm, I think this relates to the Service Abstraction principle. Deferring security-related state data helps keep the service implementation details hidden from the client.
Shelba
9 days agoSol
11 days agoRikki
13 days agoTien
14 days agoLashon
17 days agoJean
17 days agoMila
18 days agoLuann
19 days agoMike
20 days agoLashon
25 days ago