[Spread-users] connect to client in group

Andrew Holt andrew.holt at 4asolutions.co.uk
Fri Feb 22 08:03:08 EST 2008


Hi,

Thank you for the suggestions.

If a client joins group logger as logger the other(s) detect this and  
re-connect as the random ids.

Thanks again,
Andrew

On 22 Feb 2008, at 12:55, Theo Schlossnagle wrote:

> Since you are doing a cooperative setup, you are already prone to  
> being "messed with" by nodes that join (I can join as logger and do  
> nothing).
>
> Groups are ordered by Spread.  Everyone sees the group membership  
> in the same order, so you can count on that to electing leader.
>
> have all members join group "logger_ctl"
>
> On each membership change, if leader will join the "logger" group,   
> On membership changes in the "logger" group, if you are not the  
> leader of the "logger_ctl" group, leave the "logger" group.
>
> This isn't ideal, but is a workable implementation of what you  
> describe below.
>
> You should just join a group call logger, have all member receive  
> all messages and log the messages if you are the leader.  This  
> method doesn't drop logs between the membership change that the  
> success of the join of "logger" that the first method does.
>
> On Feb 22, 2008, at 7:18 AM, Andrew Holt wrote:
>
>>
>> Hi,
>>
>> I wonder if this is possible, or easily implemented, first let me  
>> set the scene:
>>
>> I have a logging client running on machine A.  It joins the group  
>> (imaginatively named) logger, with a random (e.g.tmp_1234)  
>> connection name.
>>
>> It looks at the membership list and if there is no other client  
>> named logger it reconnects as logger.
>>
>> A second client, running on machine B. joins , finds there is  
>> already a logger running and stays connected using it's random name.
>>
>> If the first client disconnects, or the machine hosting it dies,  
>> the second gets the message and re-connects as logger.
>>
>> This gives me a simple fail-over mechanism.
>>
>> Now to the question.
>>
>> I want to be able to send a message to the client logger in the  
>> group logger irrespective of the machine that its is connecting from.
>>
>> So instead of #logger#machinea something like #logger#logger.
>>
>> Any suggestions ?
>>
>> Regards,
>> Andrew
>>
>> _______________________________________________
>> Spread-users mailing list
>> Spread-users at lists.spread.org
>> http://lists.spread.org/mailman/listinfo/spread-users
>
> --
> Theo Schlossnagle
> Principal/CEO
> OmniTI Computer Consulting, Inc.
> W: http://omniti.com
> P: +1.443.325.1357 x201
> F: +1.410.872.4911
>
>
>
>
>
>
>





More information about the Spread-users mailing list