DEV Community

loading...

Discussion on: JavaScript-sprinkled Rails Applications

Collapse
citizen428 profile image
Michael Kohl • Edited

When another user requests the same page later, they will receive the cached fragment, with the unread responses of the first user.

This is something you can also avoid by using ETags (i.e. with etag { current_user.try :id }), the following article has a great summary of this and many related topics:

medium.com/rubyinside/https-medium...

I know this is not quite what you were aiming for with this article (fragment re-use and all), but I thought it's worth mentioning.