[Serdev] Concept for a SIP cluster implementation

[Andreas Granig]

> - You refer to EP1 and EP2 and then P1 and P2. I assume these are the 
> same, but referring to two different functions?  Anyway, it's a bit 
> confusing

They are the same, just an oversight, sorry.

> - The path module is still in the experimental cvs module and thus can 
> still be changed/expanded etc.  AFAIK, Path can be used to implement 
> several functionalities, but is basically the same mechanism. I hope it 
> is possible to modify the path module to work well with also your 
> scenario.  I encourage the path maintainer, Fermin Galan Marquez, and 
> you to work together on this

I already contacted Fermin a few weeks ago, and since he has another job 
now, he won't work a lot on it anymore. But I will probably steal some 
code from the path module ;o)

Also I think it logically belongs rather into the registrar module than 
into a seperated one, because it is always involved in save() and lookup().

> - From my point of view, I cannot see any reasons for why this shouldn't 
> be possible to include in HEAD once it has proven its stability in 
> experimental

See above. When integrating it into usrloc and registrar, you have the 
code exactly where the relevant things actually happen (parsing the 
REGISTER and storing the values into usrloc in save() and loading it 
from usrloc in lookup()).

When placing the code in an extra module, you have to do this parsing, 
storing and loading again, which makes no sense IMHO. And since it needs 
0.10.x because of the branch routing functionality anyway, I would 
prefer to integrate it right there.

It also won't have an impact on scenarios where no Path is used, so...

Andy