Re: [XCON] Cloning method, question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XCON] Cloning method, question



Maybe would it be good to state that in CCMP? At the moment neither the framework nor CCMP state this information. IMO it would be useful to have it somewhere. 

Thanks,

Oscar 

-----Original Message-----
From: spromano at unina.it [mailto:spromano at unina.it] 
Sent: 30. tammikuuta 2009 20:20
To: Oscar Novo
Cc: xcon at ietf.org
Subject: Re: [XCON] Cloning method, question

I think that keeping track of such changes (and hence maintaining coherence among inter-related conference objects) is part of the conference server's business logic. If we come to how the clients are notified about changes (in general), the event package should do the job (not CCMP...).

Simon

Quoting Oscar Novo <oscar.novo at ericsson.com>:

> Hi again,
>
> If we dedice to support the 'non-independent' cloning method a 
> question that arise is how the parent will notify the child about the changes?
> Which protocol will do that? CCMP, xcon-event-pachages?
>
> Oscar
>



-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano at unina.it

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/

_______________________________________________
XCON mailing list
XCON at ietf.org
https://www.ietf.org/mailman/listinfo/xcon

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.