Re: [Tipc-discussion] tipc-config is here

[Jon M. <jon...@er...>]

That is  a good summary. To the API changes should be added
that they reflect the changes in the address lookup algorithm,
such as they are described in the IETF-draft. This makes
it possible for a sender to control the lookup algorithm in a
more consistent and fine-granular way than earlier.

We still have crashes, but the list of problems is not long.
We have a commitment to present a stable version by July 1st,
and I think this is fully within reach.

/Jon

Randy Macleod wrote:

>   Hi,
>
>    I haven't been following the 1.3 dev stream until last week.
> I just got caught up on the mailing list archives.
>
> Is anything missing from the following summary of
> changes in the 1.3 stream?
>
> - api/tipc structures changed somewhat,
> - added conection flow control and 'unreliable mode'
> - linux coding style re-write,
> - many internal functions moved to native linux mechanisms
>    locks, lists, memory mgmt.
> - added finer grained locking
> - configurable zone/node/slave sizes
> - multicast support is progressing.
> - tipc-config app, eliminates ismod options...
>
>
> 1.3 seems to be unstable since the email list has crash reports...
> Are these crashes limited to multicast?
>
> When do you hope to stabilize the 1.3 development stream?
>
>
>> /Jon
>>
>>
>> hek...@ya... wrote:
>>
>>  >Hi Jon,
>>  >
>>  >That is so cool !
>>  >
>>  >I've been waiting for this for a long time. So now we can
>>  >simply "insmod tipc.o" and later on application can invoke
>>  >"tipc-config" (or some IOCTLs ?) to dynamically change
>>  >the node address ? Just want to make sure that after the
>>  >node address has been set by "tipc-config" it can still
>>  >be changed later by "tipc-config" for any time, right ?
>>  >
>>  >I'm thinking of a scenario where a cluster is formed
>>  >dynamically and the node address of an old node can be
>>  >changed to avoid conflict with a newly joined "node".
>>  >
>>  >A side issue is that I found latest CVS has only linux-2.6
>>  >support. Is linux-2.4 support planned to be dropped ?
>>  >Anyway I've ported it to linux-2.4 since I have to use 2.4
>>  >for a while.
>
>
>
> I also want to use tipc-1.3 on linux-2.4. Could these changes
> by  hek...@ya... be merged into the cvs tree?
>
>
> Keep up the good work,
>