[Spread-users] Concurrency issues with spread 4

Goran Hasse gorhas at gmail.com
Sun Sep 26 19:18:27 EDT 2010


I have used spread:s file descriptor to make an interace for g_io_add_watch
Take a look at:
In this way you can pick packets from the spread bus and do other
things at the same time.
No threads...
If you have a protocol designed over the spread buss - the standard
application protocol design rules
apply. You must check order, content and stuff.
http://www.rfc-editor.org/rfc/rfc3117.txt ;-)

Göran Hasse

2010/9/26 Johannes Wienke <jwienke at techfak.uni-bielefeld.de>:
> John Schultz wrote:
>> I believe the problem still exists and it is due to you using RELIABLE_MESS to send the following message.  RELIABLE_MESS has no ordering guarantees with respect to other messages so it can be delivered before or after the join membership message.  Indeed, different members of the group may see the same message before and after the join membership from their perspectives.
>> If you want to ensure that the message is ordered wrt all membership changes, then you should use AGREED_MESS for the service type.  Join/leave/disconnect memberships are essentially AGREED_MESS's themselves.
> Thank you very much. This makes sense.
> Regards,
> Johannes
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users

gorhas at gmail.com
Göran Hasse
Boo 229
Mob: 070-5530148

More information about the Spread-users mailing list