[Spread-users] small bug and questions

Lobiv Igor Igor.Lobiv at sitronicsts.com
Fri Jan 18 05:16:46 EST 2008


Bug:

 

Sp.c

int SP_connect_timeout(

...

      host_address = ( (i1 << 24 ) | (i2 << 16 ) | (i3 << 8) | i4 ); // bug here

 

under win32 on AMD Athlon XP 2800+ it is not work...

If string for connect is 3333 at 128.220.221.1

TCP connection goes to port 3333, IP 1.221.220.128, but it is expected "128.220.221.1"

 

I suggest use instead:

host_address = htonl(( (i1 << 24 ) | (i2 << 16 ) | (i3 << 8) | i4 ));

 

 

Questions:

 

1)       How works message synchronization - i.e. if someone sends message(MSG) to group with two members M1 and M2 is message arrived in the same time to both members or asynchronously?

2)       As I understand a message stays in some queue on spread demon(s) until all spread users in group received it. Is it true? How I can manipulate this queue - measure max load, change size, add "expired time"?

3)       How I can change the "strategy of delivery"? For example I want to implement load sharing in the group with two members M1 and M2. Odd messages process M1, even messages process M2. 

 

Best regards,

Igor Lobiv

Telco Software Development Sector

 

SITRONICS Telecom Solutions, Czech Republic a.s.

 

Tel.: +420 211 030 655,  Mobile: +420 724 936 638, Fax: +420 296 524 103 

BB Centrum - Beta, Vyskočilova 1461/2b, 140 00  Praha 4, Czech Republic

www.sitronicsts.com <http://www.sitronicsts.com/> 


DISCLAIMER
This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Top secret. Please delete it before read. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20080118/6aaa2366/attachment.html 


More information about the Spread-users mailing list