Hey Esther, All AJAX aside, why are you using AJAX to do something that could clearly be done server-side?
I mean, you're just loading *the entire page contents* based on the freakin' weekday! This can be done server-side using SSI's, PHP, or whatnot. Even if you need to work based on the visitor's TZ's weekday, HTTP headers will give you his/her GMT offset anyway... This would take <10 lines in any server-side tech. Even from an accessibility standpoint, this is *not* comfort, this is core functionality here (the whole contents!), so this should not depend on JS and AJAX being available. >From a visual standpoint, this also means that with any network latency, the visitor will first encounter an empty page, and have no visual clue that the actual contents is loading from then on... Not too good. In short, this sounds to me like a textbook case of AJAX used where it's clearly not the relevant path. Sometimes we're so bent on implementation, we forget the bigger picture. I may be wrong (not having the bigger picture), but from the problem you described, I fail to see why AJAX is needed at all! Just my two cents, -- Christophe Porteneuve a.k.a. TDD "[They] did not know it was impossible, so they did it." --Mark Twain Email: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
