Dear all, Thanks for your replies; [1] May be one way to control the network latencies is to hide the redundant servers behind a specific entity that would control this latency without adding more network overhead; [2] The question was not that general purpose, cause the non deterministic behavior I am focusing on is the application level one due to the protocol itself, as well as its proxy implementation; I mean, for some other protocols, when this behavior is limited to the session establishement for instance, it can be easily controlled through any synchronization x- level mean between the redundant nodes that are instantly consuming the same unit of incoming messages; So, putting all together, the question was was about wether the actual SIP proxy implementations limit the non deterministic behavior to the session establishment phase;
Regards, --Narjess A.; -----Message d'origine----- De : Nataraju A B [mailto:[EMAIL PROTECTED] Envoyé : jeudi 22 juin 2006 14:35 À : [EMAIL PROTECTED] Cc : AYARI Narjess RD-MAPS-LAN; [email protected] Objet : RE: [Sip-implementors] SIP Proxy non deterministic behaviour > > > [ABN] it is very unlikely that both the proxies running the same > > > software on diff machines/hardware would generate the same random > > > numbers/time based random numbers since network delay could be different > > > for same messages reaching different proxies... > > > > If they EVER generate the same 'random' number I would say that it, per > > definition, wasn't random. > > > > [ABN] I don't think so, since the combination of various parameters identify the > dialog. if it was based on a single parameter this might lead to conflicts... :) > > Please, use the quote indentation function of your e-mail client. > > You miss my point. I'm just saying that if two computers generate random > numbers that match each others then they ARE NOT RANDOM. > Really-lousy-pseudo-random, ok, but they CAN'T be considered random, per > definition. If I say "pick a number between one and ten", and I know you > will say "five" then it isn't random when you say "five". > [ABN] you are right, it's not a globally random number. See, the basic requirement is some parameters must be globally unique (for example Call-ID) and random in nature, whereas most of the parameters are random and unique within dialog/session/ something like that (tags need not to be globally unique) which are Unique and random for some duration only. Even if the same random number is generated by other entity, it's OK... as long as combination of parameter conflicts with other entities information, it's ok to have it. > /Fredrik _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
