+1 - A message queue is the best solution for this type of problem. Cheers Kai
> I think the solution is a message queue. It's a system that guarantees > the message (record) is delivered to the other system (database) and > it can give that guarantee because it stores all the messages in it's > own database. So when the remote system is unreachable the message > queue stores all the messages in order and when the remote system > comes back up, the stored messages are resent in order they where > received. > > There are a number of free open source message queues, so only issue > is how much time, effort and resources (a second server) do you what > to spend? > > > Chris > -- -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
