certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] ResignFederationExecution


From: Michael Raab
Subject: Re: [certi-dev] ResignFederationExecution
Date: Mon, 15 Nov 2010 08:08:54 +0100

Hi Eric,

>concerning Ownership (for RELEASE_ATTRIBUTES part) I'm not even
>sure the it's working now because I'm not aware of any user using
>ownership until now?

>Do you use Ownership management?
>If you only care about deleting object instance then it should doable
>relatively fast.
>If you care about Ownership too that may take longer...


I don't use ownership management, so that shouldn't block at the moment...

>You may even add a ObjectManagement::deleteAllMyObject()
>method and call it.
>This would handlde the "DELETE_OBJECTS" case.


So if I understand correctly, your proposal is to add method ObjectManagement::deleteAllMyObject() to ObjectManagement.cc.
But what would be the aim of this method? As far as I understand the federate (RTIA) doesn't know about all object instances that it holds or am I wrong? So only RTIG knows?
It looks to me that we need an additional network message type like NM_Delete_All_Objects.
What is the appropriate way to step forward? Create this message type by hand, or should this be done by some script?

Best regards,
Michael



Dipl.-Inf. Michael Raab

Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany                
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden
http://www.iff.fraunhofer.de oder http://www.vdtc.de



Von:        Eric Noulard <address@hidden>
An:        CERTI development discussions <address@hidden>
Datum:        11/12/2010 01:11 PM
Betreff:        Re: [certi-dev] ResignFederationExecution
Gesendet von:        address@hidden




2010/11/12 Michael Raab <address@hidden>:
> Hi Eric,

Hi Michael,

> seems to me that in ResignFederationExecution Service the ResignAction
> argument is ignored.

Yes this is the case.
It ignored (not used) inside

FederationManagement.cc:
void FederationManagement::resignFederationExecution(ResignAction,
TypeException &e)

> Therefore I can receive no RemoveObjectInstance callback when a federation leaves. :-(
> Is that correct?

I think it is.

> Is there a chance to fix that short term?

By me in the short term, no sorry :-(
I will be lacking time for that now.

However, as usual I may find time to review a patch.

One or two things you must know about this service is that concerned
RTIA Message is called "M_Remove_Object_Instance"
whereas
RTIG aka NetworkMessage is called  "NM_Remove_Object"

May be the easiest path for solving this would be to add
ObjectManagement::deleteObject calls
in RTIA_federate.cc when
handling Message::RESIGN_FEDERATION_EXECUTION
before the call to
fm->resignFederationExecution(RFEq->getResignAction(), e);

I think fm (FederationManagement) is not concerned by the Action (and
it is not currently uisng it)
but om (ObjectManagement) is.

You may even add a ObjectManagement::deleteAllMyObject()
method and call it.
This would handlde the "DELETE_OBJECTS" case.

enum ResignAction {
   RELEASE_ATTRIBUTES = 1,
   DELETE_OBJECTS,
   DELETE_OBJECTS_AND_RELEASE_ATTRIBUTES,
   NO_ACTION
};

concerning Ownership (for RELEASE_ATTRIBUTES part) I'm not even
sure the it's working now because I'm not aware of any user using
ownership until now?

Do you use Ownership management?
If you only care about deleting object instance then it should doable
relatively fast.
If you care about Ownership too that may take longer...


--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

--
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]