Are the any interfaces specified in CORBASEC for
controlling security context by security-aware
applications?
Extended Question:
Examples of controlling security context could be the
following:
* Switch context, a possibility of "switching
context service" between already established contexts
* Hold-on context in case of mobility
* Close/take-down context
* Re-establish context after hold-on context service
* Refresh context in case of revocation or as the
same operation as Refresh() in SecurityContext
Is This Answer Correct ? | 0 Yes | 0 No |
Can corba application have call back?
Does corba supports asynchronous communication?
What is corba? What does it do?
Explain how does corba support interoperability?
What are the reason to implement a corba application with multi-threading?
Explain does corba support distributed reference counting architectures?
Are the any interfaces specified in CORBASEC for controlling security context by security-aware applications?
What would be the most suitable ORB products when buliding a small lab for evaluating, testing and implementing security functions in a CORBA system?
Explain are there different threading models that can be used within corba servers?
What is corba good for?
What are the primary differences between RMI and CORBA?
Tell me can corba application be multi-threaded?