Post, Mark K wrote:
From what I've seen, a lot of that information is usually kept in the user's browser via cookies or "session cookies." For things that aren't, mirroring the data on separate physical devices, on separate controllers, etc., etc., provides the redundancy needed. The whole point of clustering is not to have _any_ single points of failure. That's why clustering an application is _at least_ two times more expensive than not clustering it.
Aside from users' aversion to cookies, their correct use isn't any easier than good backups;-) I reckon a lot of application authors trust the data held cookies, saying "we provided that so we know it's okay." -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
