Ruby on Rails

Walter Davis wrote in post #1106898:
> On Apr 25, 2013, at 10:37 AM, Wins Lin wrote:
>
> No, it would be any page containing unique content meant for that user's
> eyes only. You can't cache them because they are bound to the current
> user's session -- you can only cache things that are meant for everyone
> to see. No filtering or special content-creation can be going on in any
> part of cached content. Now you can use what 37Signals refers to as
> "Russian Doll" cacheing to cache parts of the page that are held in
> common, while letting other parts be dynamically generated. It's a
> yes-and sort of thing. But if you are after a win by caching the entire
> page, then it has to be essentially a static page -- same for everyone
> who views it.
>
> Walter

Thank you. Now I begin to understand the difference. But then I have
such a question. Why not to cache user's specific pages? Every user's
session has a session_id. So let it be also an id for cached content of
that particular user. Or is it cumbersome for storage to track the
content for thousand of users?

--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.