Re: Suggestion

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks Ken for your advice I think I'll go with your suggestion.

I don't want to overstay my welcome, but do you know of any source code
examples or reading material?

Yes database is a single point of failure, but that's not relevant in my
case, if the database goes down the whole company is down, if my program
goes down the users will be screaming "where is my report!", so I have to
take care of my piece of process first.


"Ken Foskey" <rmove.foskey@xxxxxxxxxxxxxxxx> wrote in message
news:48a13181@xxxxxxxxxxxxxxxxxxxx
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


.

Relevant Pages

  • Re: Tcl-Tk and network.
    ... >> that it didn't work for broadcast. ... >> the server side of this and send raw UDP packets from a compiled C ... And shows up in the "server" tclsh process: ...
    (comp.lang.tcl)
  • Re: Suggestion
    ... But if the socket server goes down all of the clients are down - single ... Use UDP and a broadcast, have all clients monitor the same UDP ... I am wondering how you don't have a central point of failure with a ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Hand Waving vs. Rigorous Analysis... (was Security Engineeringvs. Crypto Academics...)
    ... >> interuption of the broadcast communication will prevent reception during ... >> key server could prevent the user from watching the broadcast for the ... > failure than only the key server. ...
    (sci.crypt)
  • Re: client-server network
    ... the msg using sendto..then waits for a reply from the server using ... sent by server didn't reach the client...... ... Note that for broadcast, you must set the SO_BROADCAST option, which your ... UDP might not be better than TCP, ...
    (microsoft.public.vc.mfc)
  • Re: How to stop UDP port 86 BroadCast
    ... > Is it possible multipal CCITCP server can talk to each other without ... > using UDP port 86 broadcast. ... > 86 broadcast on all WAN then server-B replay it. ... you don't need more than one ccitcp2 process per LAN segment ...
    (comp.lang.cobol)