Hi Antonio,
One minor/trivial change below.
On 04/18/2012 12:27 AM, Antonio Quartulli wrote:
In the current implementation the OGM is built and filled at the moment it is
scheduled (1 originator interval before its sending). In this way, all the TT
changes happening between OGM(seqno=X) and
On Wed, Apr 18, 2012 at 10:12:42AM +0200, Martin Hundebøll wrote:
Hi Antonio,
One minor/trivial change below.
On 04/18/2012 12:27 AM, Antonio Quartulli wrote:
+ /* if we have too many changes for one packet don't send any
+* and wait for the tt table request which will be
On 04/18/2012 10:31 AM, Antonio Quartulli wrote:
On Wed, Apr 18, 2012 at 10:12:42AM +0200, Martin Hundebøll wrote:
Hi Antonio,
One minor/trivial change below.
On 04/18/2012 12:27 AM, Antonio Quartulli wrote:
+ /* if we have too many changes for one packet don't send any
+* and
On Wed, Apr 18, 2012 at 10:35:44AM +0200, Martin Hundebøll wrote:
On 04/18/2012 10:31 AM, Antonio Quartulli wrote:
On Wed, Apr 18, 2012 at 10:12:42AM +0200, Martin Hundebøll wrote:
Hi Antonio,
One minor/trivial change below.
On 04/18/2012 12:27 AM, Antonio Quartulli wrote:
+ /* if
In the current implementation the OGM is built and filled at the moment it is
scheduled (1 originator interval before its sending). In this way, all the TT
changes happening between OGM(seqno=X) and OGM(seqno=X+1) will be attached to
OGM(seqno=X+2) (because when changes happened OGM(seqno=X+1) was
