Hi AndersBj,

Reviewed the patch.
Ack.

/Neel.

On Friday 10 April 2015 06:07 PM, Anders Bjornerstedt wrote:
>   osaf/services/saf/immsv/README |  26 +++++++++++++++++++++++---
>   1 files changed, 23 insertions(+), 3 deletions(-)
>
>
> diff --git a/osaf/services/saf/immsv/README b/osaf/services/saf/immsv/README
> --- a/osaf/services/saf/immsv/README
> +++ b/osaf/services/saf/immsv/README
> @@ -397,7 +397,27 @@ restarted as a process, the call will be
>   If the OI is started after a cluster-start then these calls are necssary
>   to rebuild the implementer-map. See ticket defect ticket #543 for details.
>   (http://sourceforge.net/p/opensaf/tickets/543)
> -
> +
> +Minor discrepancy between OpenSAF and SAF on error codes for 
> admin-operations.
> +------------------------------------------------------------------------------
> +According to the SAF spec ERR_BUSY should be given as response to an
> +AdminOwnerRelease/Clear operation if there is currently an admin-operation
> +on-going directed at some object that the release/clear is targeting.
> +But The AdminOwner mechanism is an access-control mechanism, not a 
> concurrency
> +control mechanism. After access has been granted, in this case for an
> +admin-operation, there is no real point in insisting that the admin-ownership
> +must be valid until the admin-op completes. An AdminOwnerReelease/Clear will
> +return ERR_BUSY if there is an ongoing CCB, since it is unknown if additional
> +operations are to be addeded. Opeartions may be added to the CCB by the OI
> +itself using the AuggmentedCcb interface. With respect to interferference
> +from other overlapping admin-operation requests or other ccb-requests, the
> +OpenSAF IMM leaves it open to the OI implementation to handle or reject.
> +The OI dispatch is always via one single thread, but the OI may internally be
> +multithreaded. It may also postpone reply on an admin-op while taking on 
> other
> +queued callbacks, since the reply to an admin-op is not done by returning 
> from
> +the admin-op callback, but by a separate downcall to immsv.
> +
> +
>   
>   PERSISTENCE
>   ===========
> @@ -416,9 +436,9 @@ One of the main new immsv features avail
>   Persistent Back-End (PBE). By default this feature is not enabled.
>   See the instructions below for how to enable it. Use of the PBE
>   has a signifigant (negative) impact on performance for CCBs and
> -persitent runtime data, both response time and throughput.
> +persistent runtime data, both response time and throughput.
>   The upside is that the user does not need to do frequent dumps
> -to get persistence. But it is still advisable dump the IMM
> +to get persistence. But it is still advisable to dump the IMM
>   (to the imm-xml form) periodically, for backup to an external
>   filesystem, to support recovery from disasters.
>   


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to