> Does this mean that flash messages and authentication is an impossible > combination? Is there any way to work around this?
I am using Cacheable Flash for the Rails Magazine web site and it works rather well (you can see it in action on login). The trick is to page cache only pages for anonymous users (using an apache or nginx rewrite rule to detect specific cookies/authenticated users). Including Prototype or other Javascript libraries is not a huge deal as these can be cached on the client (so the transfer hit is incurred only on the first request). On the other hand it's overkill to include them solely for accessing cookies or dealing with cacheable flash. Best regards, Olimpiu On Jan 1, 1:02 pm, David Trasbo <[email protected]> wrote: > Fernando Perez wrote: > >> But nothing actually solves the problem without giving new ones. So I > >> guess I have to use fragment caching? > > We use fragment caching on our VoD website:http://www.digiprof.fr, you > > cannot do page caching if once the user is authenticated, he gets a > > custom page. > > > PS: yeah Prototype is huge, we are currently considering other lighter > > options, such as mootools. > > It would have been kind of frustrating to have 5000 lines of Javascript > hanging around just to make one thing little thing work: Cacheable > Flash. So I don't want to do that. > > I'll try fragment caching, then. Thanks! :) > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
