I'm going to have to agree that some sort of non-blocking queuing system would be a very nice feature.
Should your data source ever fail, radiator could continue to operate while losing very little function and no loss of accounting records. This may also speed radiator up, as it would just hand the data to the middleware without ever having to wait on the sql server. Thanks, Tony B, CCNA, Network+ Systems Administration GO Concepts, Inc. / www.go-concepts.com Are you on the GO yet? What about those you know, are they on the GO? 513.934.2800 1.888.ON.GO.YET -----Original Message----- From: Dan Melomedman [mailto:[EMAIL PROTECTED] Sent: Monday, June 30, 2003 9:44 PM To: [EMAIL PROTECTED] Subject: Fwd: Re: (RADIATOR) Database support fault tolerance Hugh Irvine wrote: > > Hello Dan - > > It would be fairly simple to have Radiator write to a flat file for > accounting, and then have a cron job or similar load the data into the > database periodically. You will find a simple utility to do this in the > file "goodies/radimportacct". I was hoping more for something like this included in Radiator's design. Would benefit many, really. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
