Re: Suggestion
- From: Ken Foskey <rmove.foskey@xxxxxxxxxxxxxxxx>
- Date: 12 Aug 2008 16:45:21 +1000
On Tue, 12 Aug 2008 00:32:49 -0500, Peter wrote:
Thanks Ken for your help!
But if the socket server goes down all of the clients are down - single
point of failure.
Use UDP and a broadcast, have all clients monitor the same UDP
broadcast socket. No lag time. Each one advertises which ones they pick
up.
Servers should advertise completed ones. If there is no completed and a
server is idle it should query old incomplete jobs using the same
broadcast and if there is no response pick that one up and start working
on it again (recoverability).
Note that UDP is not reliable and two could start work on exactly the
same piece at the same time. So you have to handle conflicts still, it
just reduces the probability.
I am wondering how you don't have a central point of failure with a
Database anyway?
Ken
.
- Follow-Ups:
- Re: Suggestion
- From: Peter
- Re: Suggestion
- References:
- Suggestion
- From: Peter
- Re: Suggestion
- From: Ken Foskey
- Re: Suggestion
- From: Peter
- Suggestion
- Prev by Date: Re: Static vs Instance Method Question
- Next by Date: Re: Static vs Instance Method Question
- Previous by thread: Re: Suggestion
- Next by thread: Re: Suggestion
- Index(es):
Relevant Pages
|