[Tipc-discussion] Re: TIPCv2 test spec!

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

Hi,
NAME_AVAILABLE is still there, but is now called
TIPC_BLOCK_SUBSCRIBE. What really has been removed
is the "preferred/load shared" options when you publish a port
name sequence. Instead, this selection is now done by the caller, by
indicating a "lookup domain" (it is described in the IETF draft).
The lookup domain decides whether the "closest first" (~ preferred) or
"round robin" (~load shared) algorithms should be used, but also
how far out in the network the algorithm should be looking.

There exists no design spec for the current version of TIPC, so
you will have to do with the IETF draft and the code for now :-)

Regards /jon

Yin, Hu wrote:

>Hi,
>
>As you know there is a test spec for TIPCv1, but now TIPC has gone to
>v2. Some of the items in test spec for TIPCv1 are not suitable or don't
>work for TIPCv2. For example, the following is some of the content:
>------------------------------------------------------------------------
>----
>------------------------------------------------------------------------
>----
>Name Table Test Program
>-----------------------
>
>1) Publish 1000 port names, some of them from the same port.
>2) Call NAME_AVAILABLE to verify that the names are really
>   published.
>2) Withdraw these port names in a different order than they 
>   were published.
>2) Call NAME_AVAILABLE to verify that the names are really
>   withdrawn.
>3) Publish different types:
>     Load shared. Many from same processor, and from
>                 different processors
>     Preferred load shared.Verify that you are refused a 
>                  second publication.
>     Illegal suite: lower > upper
>     Overlapping suites: Verifiy that these are rejected.
>     Publications with different visibility: Zone,Subnet,Processor
>              Call NAME_AVAILABLE again to verify publication scope.
>------------------------------------------------------------------------
>----
>------------------------------------------------------------------------
>----
>
>but you know there is not a NAME_AVAILABLE event in TIPCv2 source code
>at all. So I think we'd better update and improve the old test spec from
>v1 to v2. Is there a new test spec for TIPCv2 or not? If not, I'd like
>to work out a test spec for TIPCv2 according to v1, but I need more
>information about TIPCv2, such as the design spec and etc. So can you
>provide me some good materials and help me to work out that together,
>thank you very much in advance!
>
>Best Regards
>
>Nick Yin
>
>Jun 2, 2004
>  
>